tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 43552] New: - Memory leak on application reload apparently caused by commons-pool 1.3
Date Thu, 04 Oct 2007 15:02:06 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43552>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43552

           Summary: Memory leak on application reload apparently caused by
                    commons-pool 1.3
           Product: Tomcat 5
           Version: 5.5.24
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: major
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: cott@internetstaff.com


I am seeing commons-pool's EVICTION_TIMER causing applications not to unload,
using Edward Chou's modified JHAT that assists in tracking classloader leaks.

--> java.lang.reflect.Method@0x2aaab4902360 (145 bytes)  (field clazz:) exclude
--> class org.apache.catalina.startup.Catalina (160 bytes) (??:) exclude
--> org.apache.catalina.loader.StandardClassLoader@0x2aaab482c6e8 (123 bytes)
(field parent:) exclude
--> org.apache.catalina.loader.StandardClassLoader@0x2aaab480eab0 (123 bytes)
(field classes:) exclude
--> java.util.Vector@0x2aaab4815d98 (36 bytes) (field elementData:) exclude
--> [Ljava.lang.Object;@0x2aaab4b545f8 (10256 bytes) (Element 21 of
[Ljava.lang.Object;@0x2aaab4b545f8:) exclude
--> class org.apache.tomcat.dbcp.pool.impl.GenericObjectPool (160 bytes) (static
field EVICTION_TIMER:) exclude
--> java.util.Timer@0x2aaab4732740 (40 bytes) (field thread:) exclude
--> java.util.TimerThread@0x2aaab494fa80 (173 bytes) (field contextClassLoader:)
exclude
--> org.apache.catalina.loader.WebappClassLoader@0x2aaab482b4e8 (288 bytes) exclude 

This appears to be directly related to the upgrade to commons-pool 1.3 in both
Tomcat 5.5.24 and Tomcat 6.0.11. Copying the commons-pool 1.2 based JAR from
Tomcat 5.5.20 seems to solve the problem in 5.5.25 and 6.0.14 with no readily
apparent side effects in my admittedly limited testing of my own apps.

This has been reported in https://issues.apache.org/jira/browse/POOL-97 but
doesn't appear to be rapidly heading towards a solution.

Any chance of reverting to 1.2 to fix this leak?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message