Marcelo; You are probably exhausting all your connections in the pool. Make sure all your connections are returned back to the pool at the end of a "finally" block. That way the connection is returned to the pool regardless of whether your database work was a success or not. Also, while you are developing, keep the number of connections in the pool restricted to 1. That way you can easily verify that you are always returning connections back..
A while back a long discussion was held here relating to just this issue.. you may want to search the archives.. (let me know if you cant find the discussion..) Regards, Geeta Marcelo Epstein wrote: > Hi, > > I have just started using Connection Pooling in my app (Tomcat, Struts, DBCP, > Mysql) . > It woks for about 20 hours and stop working until tomcat restart. > > I get this exception: > > org.apache.commons.dbcp.SQLNestedException: Cannot get a connection, pool exhausted, > cause: > java.util.NoSuchElementException: Timeout waiting for idle object > > I canīt fix it. Any advice?? > > Thanks in advance. > Marcelo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
