Re: Is this a classloader leak?

> by Full GC? Definitely they have some reference(s) from somewhere. All > I can see that they were loaded by 'class loader 0x21005760a > 'org/apache/catalina/loader/WebappClassLoader'. Is this another form > of classloader leak or something else? Any idea?

Is this a classloader leak?

loaded by 'class loader 0x21005760a 'org/apache/catalina/loader/WebappClassLoader'. Is this another form of classloader leak or something else? Any idea? Environment: Windows 2012 server, JDK 1.8_92, Tomcat 7.0.55

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

Sorry, you are right, it is in org.apache.tomcat.util.modeler.BaseModelMBean, and resource attribute it is retaining is an org.apache.commons.dbcp.BasicDataSource Diego Caldarale, Charles R escribió: From: Diego Rodríguez Martín [mailto:[EMAIL PROTECTED] Subject: Re: Tomcat 6 classloader

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_

RE: Classloader leak

Ok the problem has been created and the example war attached. http://issues.apache.org/bugzilla/show_bug.cgi?id=42172 -Original Message- From: Mark Thomas [mailto:[EMAIL PROTECTED] Sent: Thursday, April 19, 2007 7:18 AM To: Tomcat Users List Subject: Re: Classloader leak

Re: Classloader leak

Gross, Keith wrote: > I'll need to strip the application of some confidential bits but since my > test case only required the menu page that shouldn't be a problem. Once I > have a test case were would you like it placed? Please create a bugzilla entry for it and add the war as an attachment. ht

RE: Classloader leak

, April 17, 2007 6:05 PM To: Tomcat Users List Subject: Re: Classloader leak Gross, Keith wrote: > Is there some way to prevent this? It could be application error or it could be a Tomcat bug. Can you create a simple war that demonstrates the issue I can use for deb

Re: Classloader leak

Isn't it a known problem that if you redeply a webapp using tomcat admin tool, the older class definitions are not dumped from the memory hence causing the memory leak ?? I dont remember but I read it somewhere. Gaurav Singh Kushwaha http://www.chakpak.com Ph: +91-9880110695 Bangalore, India. On

Re: Classloader leak

Gross, Keith wrote: > Is there some way to prevent this? It could be application error or it could be a Tomcat bug. Can you create a simple war that demonstrates the issue I can use for debugging? Mark - To start a new topic, e-

Classloader leak

I'm running Tomcat 5.5.23 on Java 1.6.0_01 on Windows. During testing I've noticed that memory usage rises steadily with each redeploy of an application. After each redeploy Jconsole reports the number of loaded classes has risen and the memory use in the PermGen has increased. Tomcat is the bina