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=42856>. 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=42856 Summary: Memory leak using my own factory in a dbcp resource Product: Tomcat 6 Version: unspecified Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Catalina AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Commons-pool version 1.3, embbeded in Tocamt, has a memory leak (https://issues.apache.org/jira/browse/POOL-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484747) Trying to avoid this memory leak, I deployed older versions of commons-pool and commons-dbcp in lib directory, and I defined my own factory attribute in a dbcp resource in context.xml. <Resource name="jdbc/ApplicationPool" auth="Container" factory="org.apache.commons.dbcp.BasicDataSourceFactory" type="javax.sql.DataSource" driverClassName="org.postgresql.Driver" url="jdbc:postgresql://DatabaseHost/DatabaseFile" username="DatabaseUser" password="DatabasePassword" maxActive="20" maxIdle="10" maxWait="-1"/> Doing some memory profiling, Tomcat still isn't releasing de pool properly. The offending class is "org.apache.tomcat.util.modeler.BaseModelMBean". It is retaining the pool in its "resource" attribute. You can follow the discussion thread about this issue in tomcat-users list http://www.mail-archive.com/[EMAIL PROTECTED]/msg30838.html -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
