cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SANSONE, AARON M [AG-Contractor/1000]" <>
Subject RE: Datasource pooling issue. Connections exceed limit. Resolved .
Date Thu, 20 Jun 2002 16:32:02 GMT

As it turns out, we were the victims of a renegade servlet that wasn't
closing it's connection.  We mistakenly thought it was Cocoon.

Thanks for your help,


> -----Original Message-----
> From: Tom Klaasen []
> Sent: Wednesday, June 19, 2002 9:26 AM
> To:
> Subject: Re: Datasource pooling issue. Connections exceed limit.
> Hmm, looks like a bug has re-emerged.
> When I was working on SQLTransformer last year, I had this 
> bug also. And 
> I succeeded in solving it.
> However, there has been made some adaptions to SQLTransformer lately 
> (not by me) that might have created the bug again. 
> SQLTransformer isn't 
> the easiest code IMHO (it's on the crossing of 3 or more 
> 'streams' that 
> you have to keep an eye on -- SAX stream, stream of calls to 
> the DB, and 
> stream of life of the object itself, to name a few).
> Unless someone else stands up with a solution, I think you 
> can post this 
> as a bug (with all necessary information to reproduce it) or even 
> better, if you consider yourself a good programmer ;-) , you 
> can post a 
> patch.
> The solution is probably in the conn.close() that is somewhere in the 
> code, but is never called. I think you have to look in that direction.
> If this isn't the case, maybe even the underlying pooling 
> mechanism is 
> broken (although this would surprise me, because that pooling 
> mechanism 
> is used on more than one place).
> I wish you good luck with the bug hunting!
> tomK

Please check that your question  has not already been answered in the
FAQ before posting.     <>

To unsubscribe, e-mail:     <>
For additional commands, e-mail:   <>

View raw message