File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Websphere and the fly likes JCA, Connection pooling and WebSphere v5 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "JCA, Connection pooling and WebSphere v5" Watch "JCA, Connection pooling and WebSphere v5" New topic

JCA, Connection pooling and WebSphere v5

Kev D'Arcy
Ranch Hand

Joined: Jul 26, 2001
Posts: 75
I've been investigating the use of JCA resource adapters running under
WebSphere v5. I've been able to muddle my way through up to this point
(no thanks to the dismal documentation from IBM!) and have managed to
get a test connector working properly, apart from the connection pooling
WebSphere is managing the connection pooling fine (or so it would seem)
and creating the connections as required. But, if I have the maximum
connections set to 2 for example, when I send in a third request, WebSpere
times out telling me that there are no more connections available. It
seems that the first two connections that are created, never get returned
to the pool and get lost in some sort of void, never to be seen again.
Am I doing (or not doing as the case may be!) something wrong? Is there
something I should be doing to get the created connections returned to
the pool? Any help on this would be greatly apprectiated!!
Chris Mathews
Ranch Hand

Joined: Jul 18, 2001
Posts: 2712
Moving to the IBM/Websphere Forum...
Kyle Brown
Ranch Hand

Joined: Aug 10, 2001
Posts: 3892
Just out of curiosity, are you closing the first two connections when you are done with them? That's how they're returned to the pool...

Kyle Brown, Author of Persistence in the Enterprise and Enterprise Java Programming with IBM Websphere, 2nd Edition
See my homepage at for other WebSphere information.
I agree. Here's the link:
subject: JCA, Connection pooling and WebSphere v5
It's not a secret anymore!