Re: Tomcat 6 classloader leak in Commons Pool

Hi, I have tried what you suggested but it doesn't release the context properly. The method in Registry is unregisterComponent (unregister doesn't exist) ObjectName on = new ObjectName("Catalina:type=DataSource,path=/myapp,host=localhost,class=org.apache.commons.dbcp.BasicDataSource,name=

Re: Tomcat 6 classloader leak in Commons Pool

leak in Commons Pool I have found that the offending class causing the leak is org.apache.tomcat.util.modeler.ManagedBean. It keeps two attributes referencing my dbcp pool, called resource and resourceType. Are you sure about that class name? It looks like the fields you've ment

Re: Tomcat 6 classloader leak in Commons Pool

"Diego Rodríguez Martín" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi, > >I have been making some more tests about this issue, using old > dbcp/pool factory to get rid of the memory leaks of tomcat embedded > libraries commons-pool/commons-dbcp > >When using my own f

RE: Tomcat 6 classloader leak in Commons Pool

> From: Diego Rodríguez Martín [mailto:[EMAIL PROTECTED] > Subject: Re: Tomcat 6 classloader leak in Commons Pool > > I have found that the offending class causing the leak is > org.apache.tomcat.util.modeler.ManagedBean. It keeps two > attributes referencing my dbcp pool, c

Re: Tomcat 6 classloader leak in Commons Pool

Hi, I have been making some more tests about this issue, using old dbcp/pool factory to get rid of the memory leaks of tomcat embedded libraries commons-pool/commons-dbcp When using my own factory for dbcp and commons pool (the old versions), I clear the resources used invoking datasou

Re: Tomcat 6 classloader leak in Commons Pool

Hi, I have found what you said about the factory. It is ported to 6.0. I have tried to use the old commons-dbcp library, copying commons-pool-1.2.jar and commons-dbcp-1.2.2.jar in tomcat lib directory and defining the attribute factory="org.apache.commons.dbcp.BasicDataSourceFactory" in th

Re: Tomcat 6 classloader leak in Commons Pool

In older versions of tomcat (5.0.x) there is a factory attribute defining the pool to use. It's unclear from the limited look I did whether that was carried forward to 5.5 and 6.0. --David Diego Rodríguez Martín wrote: Hi, Is there any way to fix this leak downgrading the version of com

Re: Tomcat 6 classloader leak in Commons Pool

Hi, Is there any way to fix this leak downgrading the version of commons pool. I have a production enviroment where we have a lot of deploy/undeploy and with this leak we have to stop/start Tomcat very often. Is there a possibility of replacing tomcat-dbcp.jar with the older individual jar

Re: Tomcat 6 classloader leak in Commons Pool

On 6/8/07, Diego Rodríguez Martín <[EMAIL PROTECTED]> wrote: It affects version 1.3 of commons pool. In tomcat 6, commons pool is embbeded in /tomcat-dbcp.jar/, and the docs don't say with version of commons is inside. It's that version. A new commons-pool version will be integrated when it's a

Tomcat 6 classloader leak in Commons Pool

Hi, I have a webapp that is running ok under tomcat 5.5. I have upgrade to Tomcat 6 and I have found a big memory leak because WebAppClassLoader gets never garbage collected. I have used a profiler and have found that the object that is stopping the garbage collector could be EVICTION_