Thats what i've been thinking. after we obtain results in a resultset and before we start iterating through it, the original connection is somehow getting closed. it could be because some other user has a reference to the same connection. but i'm not sure how that can happen. all connections are local variables in action classes (i'll double check this). i've also synchronized the getConnection method on the pool.
-----Original Message----- From: Phillip Qin [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 3:36 PM To: 'Struts Users Mailing List' Subject: RE: [OT] DBCP Pool Closed connection problem Would it be a multi-threading problem, another user moves cursor to next row of the ResultSet? Regards, PQ "This Guy Thinks He Knows Everything" "This Guy Thinks He Knows What He Is Doing" -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: February 27, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: RE: [OT] DBCP Pool Closed connection problem Thanks for the replies. How can turn on the validation which checks for a good connection before returning. I guess i need to setTestOnBorrow(true). Do I need to do any thing else? We actually have automated JTest which checks for all closed connections. So that's what makes me certain that connections are all closed properly. What i did is that i made only one connection available to the pool. and when i'm the only user, things work fine even with one available connection. -----Original Message----- From: Miller, Jason [mailto:[EMAIL PROTECTED] Sent: Thursday, February 27, 2003 2:57 PM To: 'Struts Users Mailing List' Subject: RE: [OT] DBCP Pool Closed connection problem 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] > --------------------------------------------------------------------- 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]
