I'm not really sure you are going to have problems but to me it seems not a
good way of accessing your DB.
For each resultSet (query, or whatever) use another connection until you are
finished with the resultset and then put it back in the pool and reuse when
necessary. This is the way I work and then you will not have any other
So in your servlet create a pool, make sure there is only one pool active,
initialize in the servlet init method and use your pool to get a connection
every time you have a new request, when your rquest is finished the put it
back in the pool.
Thomas De Vos
> If multiple threads, say from several instances of a servlet, are
> statements on a shared connection will the results be corrupted? Is there
> performance benefit to having multiple connections through a connection
> if there is no corruption? Would use of a shared connection to create sql
> statements need to be synchronized?
> Thank you for your help,
> Ben Fornshell