These are the main 2 reasons that come to me: (1) You are not "closing" the connection once you've finished using it. This signals the pool's manager when to re-assign that connection (i.e. you've finished, so it can be used by someone else).
(2) Your connection pool is not big enough. HTH, Freddy. -----Mensaje original----- De: Marcelo Epstein [mailto:[EMAIL PROTECTED] Enviado el: martes, 06 de abril de 2004 18:09 Para: Struts Users Mailing List Asunto: Connection Pooling 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]
