+1
See you a chance the commons dbcp or pool team fix the bug and we can
use a newer version?
Regards
Peter
Am 01.12.2007 um 21:24 schrieb Mark Thomas:
All,
The update to commons-pool-1.3 has caused a memory leak[1].
Further, [2]
suggests it may cause reload issues in some circumstances.
The release note [3] for commons-pool-1.3 does indicate a large
number of
bugs have been fixed compared to commons-pool-1.2. That said, I do not
believe we upgraded to 1.3 to fix a specific Tomcat bug. Therefore, I
propose we revert to commons-pool-1.2 for the next release of each
version.
Mark
[1] http://issues.apache.org/bugzilla/show_bug.cgi?id=43552
[2] https://issues.apache.org/jira/browse/POOL-97
[3] http://commons.apache.org/pool/release-notes-1.3.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
