needed a known
necessity with connection pooling or is this just a 'better safe than
sorry'
recommendation? I always thought that the connection itself was the only
thing that needed releasing. Please tell me if that's incorrect.
Thanks.
Neal
-Original Message-
From: p22
tell me if that's incorrect.
Thanks.
Neal
-Original Message-
From: p22 [mailto:p22;hotmail.com]
Sent: Sunday, October 27, 2002 6:56 PM
To: Tomcat Users List
Subject: Re: DBCP - connection pool exhausted
1. make sure that you have closed all the resultset, stmt
try -1
- Original Message -
From: Nicholas Orr [EMAIL PROTECTED]
To: Tomcat Mailing List [EMAIL PROTECTED]
Sent: Sunday, October 27, 2002 7:39 PM
Subject: Tomcat Connection Pooling Question
Hi,
Is there a way to make the maxWait to just wait till there is an available
connection??
1. make sure that you have closed all the resultset, stmt and connections
after use.
2. set removeabandonto recover those unclosed resource.
3. make sure you are not reading at the end of the result set.
- Original Message -
From: neal [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL
