RE: JDBC Connection Pooling

["DUCRET Gilles (GVA)" <Gilles.DUCRET@xxxxxxxxxxxxx>]

Make sure that all the ressources opened during the use of the connection object have been closed before the object is released.

 

I suggest you to use the Data Access Beans provided by IBM. They have caching features allowing you to read the result set even if

it is closed (In fact you don't read the resultset, but a cache object containing the result).

 

Gilles

-----Original Message-----
From: Steve Raisor [mailto:sraisor@earthlink.net]
Sent: vendredi, 29. juin 2001 19:17
To: java400-l@midrange.com
Subject: JDBC Connection Pooling

Hi everyone!

 

    I'm fairly new to java and have a quick question I hope someone can answer.  We are using Websphere 3.5 and up until this point have been using JDBC without connection pooling.  Now I am tinkering with connection pooling and have a question.  Does connection pooling leave locks on the files that it accesses?  It seems to be on my system.  If so, does that mean the only way to make database changes (using sql) is to shutdown the Websphere application?  Or, is my implementation trying to use connection pooling incorrect in some way?

 

Thanks for your help in advance!

Steve Raisor



**********************************************************************
This E-mail and any files transmitted with it are confidential
and intended for the exclusive use of the addressee(s) only.
You should not disclose its contents to any other person.
If you are not the intended recipient please notify the sender
immediately.
**********************************************************************