You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mark Thomas <ma...@apache.org> on 2007/12/01 21:24:16 UTC
[PROPOSAL] Revert to commons-pool-1.2
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [PROPOSAL] Revert to commons-pool-1.2
Posted by Mark Thomas <ma...@apache.org>.
Peter Rossbach wrote:
> +1
>
> See you a chance the commons dbcp or pool team fix the bug and we can
> use a newer version?
Looking at the history of the issue, I am guessing not in the short term.
I'll see what I can do to help out (if anything) to speed along a 1.4 release.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [PROPOSAL] Revert to commons-pool-1.2
Posted by Peter Rossbach <pr...@objektpark.de>.
+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: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: [PROPOSAL] Revert to commons-pool-1.2
Posted by Remy Maucherat <re...@apache.org>.
On Sat, 2007-12-01 at 20:24 +0000, Mark Thomas wrote:
> 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.
I disagree with that plan. If someone needs to fix this specific issue,
they can easily configure a different version of the connection pool,
this avoids reintroducing unpecified issues to the pool.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: [PROPOSAL] Revert to commons-pool-1.2
Posted by Bill Barker <wb...@wilshire.com>.
Doing some Gump work reminded me: Once we upgrade to the next version of
DBCP, that will add a dependancy on JTA. Gump caught this in July, and I
added the dependancy to Gump then. We can probably just use Geronimo's
version for Tomcat, but I thought I should send out a heads-up, in case
there are people who ignore Gump nags :).
"Mark Thomas" <ma...@apache.org> wrote in message
news:4751C2F0.9060509@apache.org...
> 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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org