Just a guess, but maybe this occurs while filling the connection pool with connections at the very beginning. Assume your connection pool manager was set up to open at least 100 connections. In case your SQL server at work doesn't allow that much connection or some other clients are using some already you might receive this error. Maybe check with your admin at work how many simultanious connection that sql db can serve. Maybe it's simply limited. You could also try to open a few connections "manually" to find out when your db says "no more".
> -----Original Message----- > From: Barclay A. Dunn [mailto:[EMAIL PROTECTED]] > Sent: Montag, 27. Januar 2003 19:21 > To: [EMAIL PROTECTED] > Subject: java.sql.SQLException: DBCP could not obtain an idle > connection, pool exhausted > > > i have set up Tomcat 4.1(.12, i think) with DBCP native, > connecting to Sql Server 2000 on a remote machine. with the > same configuration at home i get connected just fine. at > work, i get this error: > > java.sql.SQLException: DBCP could not obtain an idle > connection, pool exhausted > > i'm getting this error upon first use of the database, so i > do not think it's a problem with not closing connections > previously in use. the only difference in configurations, now > that i think about it, is i have apache running in front of > tomcat on my box at work, but not at home. could that be it? > > does anybody know how to solve this? > > thanks > barclay > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
