I had this problem once. At the time, I was positive everything was closed correctly, but it turned out at one point, where I was unwrapping the connection, I had closed it. This inadvertently caused the pool to be exhausted.
This occurred before I had a quality check on my connections, so it didn't replace the closed ones. Still, check exhaustively before you say you are positive all closings are correct. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 3:52 PM > To: [EMAIL PROTECTED] > Subject: [OT] DBCP Pool Closed connection problem > > > Hi, > I'm using commons DBCP in conjuction with STRUTS. > When a lot of users start using our application, we > start getting a > lot of exceptions related to Connections, like "Exhausted > Resultset" or > "Connection is Closed". The first one happens when we try to > retrieve a > column from a resultset. The second one happens when we try to open a > connection. > Neither of these errors happen in a predictable fashion. > Right now we have set the pool max active connections > to 50 and the > number of users testing is about 5. > I'm absolutely positive, that all connections, resultsets and > statements have been closed at the appropriate places by the pool. > Is it a problem with the way I've configured the pool? > has anyone > faced a similar problem before? > > Thanks, > Gaurav > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
