Your "username with bad password" problem has been fixed: http://issues.apache.org/bugzilla/show_bug.cgi?id=18905
I don't find your "close method" bug report. The other issue you reported (also fixed) was: http://issues.apache.org/bugzilla/show_bug.cgi?id=18921
There is a dependency on pool but not on lang. The pool component will be released together with DBCP.
Dirk
srinath narasimhan wrote:
One of the bugs in the Jdbc2PoolDataSource was it was caching connections based on the user name alone (even connections with wrong password), so if the first request to the pool was a username with bad password, then the pool had the bad connection and was returning it for further connections. So I had to reset the pool ( in my case restart tomcat ). I had filed this as a bug, do you know if that was included in this new version ? Another one was the close method was not really closing connections. I was also running into dependency issues with pool and lang.
Thanks.
-----Original Message----- From: Dirk Verbeeck [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2003 16:55 To: Jakarta Commons Users List Subject: Re: [DBCP][Pool] Ready for release
Good question, I don't know if the "updated version" is ready. It doesn't have any open issues and no failing test so nothing is stopping us but maybe the author can give his blessing.
Dirk
srinath narasimhan wrote:
Does this release include the Jdbc2PoolDataSource or its updated version ?
Thanks.
--------------------------------------------------------------------- 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]
