JCA, Connection pooling and WebSphere v5

Hi,
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
element.
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!!
Thanks,
Kev.

Moving to the IBM/Websphere Forum...

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