Re: Tomcat 4.1 Connection Pooling...

[Michael J. Makunas]

Just a thought (and I apologize if this was already mentioned.....I 
missed the very beginning of the thread), but I would also make sure you 
have the latest connection pooling jars. I recently had a problem where 
even though I had the tomcat configured to reclaim abandoned 
connections, some were still remaining open. Turned out there was a bug 
in the dbcp jar and upgrading to the latest solved it.

-Michael
Dale, Matt wrote:
Every time your application uses a connection it should call the close() method to 
return it to the pool. I had a similar problem where over a fairly short period of 
time there was a database error which caused the execute to throw an exception. I had 
forgotten to put a finally block in that section so the connection never got closed. 
Once I put a finally block in with a con.close() then it solved my problem.
Ta
Matt
-----Original Message-----
From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
Sent: 28 September 2004 20:04
To: Tomcat Users List
Subject: RE: Tomcat 4.1 Connection Pooling...
how can i check that and how to resolve it...
-----Original Message-----
From: Dale, Matt [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 28, 2004 3:06 PM
To: Tomcat Users List
Subject: RE: Tomcat 4.1 Connection Pooling...

Perhaps your application is hanging on to the database connections and not
returning them to the pool?
-----Original Message-----
From: Shilpa Nalgonda [mailto:[EMAIL PROTECTED]
Sent: 28 September 2004 19:43
To: Tomcat Users List; Peter Lin
Subject: RE: Tomcat 4.1 Connection Pooling...
I have updated with classes12.jar, but still i have this problem.  But Peter
what ii sthe bug that you
mentioned, i have the problem of
java.sql.SQLException: ORA-00020: maximum number of processes (200) exceeded
--
** Michael J. Makunas ** http://www.makunas.com/ **
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]