Yes, it should be OK if you close the pool connection at the
appropriate time and don't close the one from getInnermostDelegate -
the pool takes care of that one.
--
Len
On Feb 18, 2008 2:48 PM, Petter Olofsson <[EMAIL PROTECTED]> wrote:
> Hi Len! Thanks for the reply.
> The dconn was closed by s
Hi Len! Thanks for the reply.
The dconn was closed by simply calling the close function when I was
done with the connection.
This is something that has worked in the past so I'm a bit confused
when it stopped working now.
I have solved the problem now by just returning the connection from
the pool
It looks to me like you're bypassing the connection pool and messing
up the way it handles connections. You've only shown a snippet of
code, so I have a couple of questions:
1. After dconn is returned from getConnection, how and when does it get closed?
2. Does the exception happen every time getCo
