Description of problem: Tomcat 6.0.26 in f14 build with version 1.3 of commons-pool in package jakarta-commons-pool-tomcat5. This version has well known performance problems (especially POOL-75 https://issues.apache.org/jira/browse/POOL-75). However, upstream Tomcat 6.0.26 comes with commons-pool 1.5.4, that fixes that problem and have a lot of other improvements. Version-Release number of selected component (if applicable): tomcat6-6.0.26-8.fc14.noarch jakarta-commons-pool-tomcat5-1.3-13.fc13.x86_64
This bug shouldn't be against tomcat6 but against jakarta-commons-pool package to be updated to latest version because tomcat is simply using the system-wide jakarta-commons-pool. Preferably renamed to apache-commons-pool too. Changing component.
tomcat6-6.0.26-13.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/tomcat6-6.0.26-13.fc14
tomcat6-6.0.26-14.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/tomcat6-6.0.26-14.fc14
tomcat6-6.0.26-14.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tomcat6'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/tomcat6-6.0.26-14.fc14
tomcat6-6.0.26-14.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
Yes, installing tomcat6-6.0.26-14.fc14 still installs jakarta-commons-pool-tomcat5-1.3-13.fc13 in fedora 14 stable.
I am not speaking for the maintainer, but this has already been fixed in rawhide and has nothing to do with tomcat itself (that's why I renamed this bug).
Jakarta-commons-pool is named apache-commons-pool of version 1.5.5 in rawhide. I propose leaving F-14 as is and simply install the rawhide package if you need it.
Please keep in mind that there is two packages that contains Apache Commons Pool. First package is jakarta-commons-pool, that contains classes in package "org.apache.commons.pool". The second is jakarta-commons-pool-tomcat5. It is repackaged version of Commons Pool, java package is "org.apache.tomcat.dbcp.pool". Tomcat uses second package. I think it is done to prevent conflicts with web applications that may contain its own commons-pool in its WEB-INF/lib
Version 1.5.6 is in F15, closing.