Thanks, Dan. You learn something new every day :)
David
Daniel John Debrunner wrote:
David Van Couvering wrote:
Well, more information on this. It appears if I call getConnection() twice on the *same* XAConnection or PooledConnection(), the first connection is closed as soon as I get the second connection. I am not sure if this is a bug.
Not a bug, defined by the JDBC spec.
Extract from JDBC 3.0 section 11.4
"Any previously existing Connection object is automatically closed when the associated PooledConnection.getConnection method is called."
Dan.
