You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Sanka, Ambica" <AS...@ATPCO.NET> on 2016/05/20 12:55:06 UTC
memory leak in Tomcat 8.0.9
Support Team,
We have been using Tomcat 8.0.9 for our applications. We noticed below memo= ry leak error and out tomcat could not stopped. We had to kill the process = manually. I was reading articles in the internet and this got address after= tomcat 6. But we found error in higher versions. We are not sure where to = fix this? Below is the error we are getting
2016-05-19 14:03:31,161 [localhost-startStop-2] WARN org.apache.catalina.l=
oader.WebappClassLoader- The web application [/fmDirectoryService] appears = to have started a thread named [Thread-6] but has failed to stop it. This i= s very likely to create a memory leak. Stack trace of thread:
java.lang.Thread.sleep(Native Method)
net.atpco.cluster.support.BaseLocator$AdminTask.run(BaseLocator.java:141)
2016-05-19 14:03:31,197 [localhost-startStop-2] INFO org.apache.catalina.c=
ore.ContainerBase.[Catalina].[localhost].[/fmbootstrap]- Destroying Spring = FrameworkServlet 'dispatcherServlet'
2016-05-19 14:03:31,210 [localhost-startStop-2] INFO org.apache.catalina.c=
ore.ContainerBase.[Catalina].[localhost].[/fmbootstrap]- Closing Spring roo= t WebApplicationContext
2016-05-19 14:03:31,210 [localhost-startStop-2] INFO org.springframework.b=
oot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext- Closing= org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebAppli=
cationContext@5e119034<mailto:org.springframework.boot.context.embedded.Ann<mailto:cationContext@5e119034%3cmailto:org.springframework.boot.context.embedded.Ann>=
otationConfigEmbeddedWebApplicationContext@5e119034>: startup date [Thu May=
19 08:17:39 EDT 2016]; root of context hierarchy May 19, 2016 2:03:31 PM com.mongodb.util.management.jmx.JMXMBeanServer unre= gisterMBean
WARNING: Unable to register MBean org.mongodb.driver:type=3DConnectionPool,=
clusterId=3D1,host=3Dlocalhost,port=3D27017
javax.management.InstanceNotFoundException: org.mongodb.driver:type=3DConne=
ctionPool,clusterId=3D1,host=3Dlocalhost,port=3D27017
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(D=
efaultMBeanServerInterceptor.java:1095)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveU=
nregisterMBean(DefaultMBeanServerInterceptor.java:427)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregister=
MBean(DefaultMBeanServerInterceptor.java:415)
at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanS=
erver.java:546)
at com.mongodb.util.management.jmx.JMXMBeanServer.unregisterMBean(J=
MXMBeanServer.java:52)
at com.mongodb.JMXConnectionPoolListener.connectionPoolClosed(JMXCo=
nnectionPoolListener.java:68)
at com.mongodb.PooledConnectionProvider.close(PooledConnectionProvi=
der.java:107)
Any kind of help is appreciated.
Thanks
Ambica.
Re: memory leak in Tomcat 8.0.9
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
On Fri, May 20, 2016 at 2:55 PM, Sanka, Ambica <AS...@atpco.net> wrote:
> Support Team,
>
> We have been using Tomcat 8.0.9 for our applications. We noticed below
> memo= ry leak error and out tomcat could not stopped. We had to kill the
> process = manually. I was reading articles in the internet and this got
> address after= tomcat 6. But we found error in higher versions. We are not
> sure where to = fix this? Below is the error we are getting
>
> 2016-05-19 14:03:31,161 [localhost-startStop-2] WARN
> org.apache.catalina.l=
>
> oader.WebappClassLoader- The web application [/fmDirectoryService] appears
> = to have started a thread named [Thread-6] but has failed to stop it. This
> i= s very likely to create a memory leak. Stack trace of thread:
>
> java.lang.Thread.sleep(Native Method)
>
> net.atpco.cluster.support.BaseLocator$AdminTask.run(BaseLocator.java:141)
>
> 2016-05-19 14:03:31,197 [localhost-startStop-2] INFO
> org.apache.catalina.c=
>
> ore.ContainerBase.[Catalina].[localhost].[/fmbootstrap]- Destroying Spring
> = FrameworkServlet 'dispatcherServlet'
>
> 2016-05-19 14:03:31,210 [localhost-startStop-2] INFO
> org.apache.catalina.c=
>
> ore.ContainerBase.[Catalina].[localhost].[/fmbootstrap]- Closing Spring
> roo= t WebApplicationContext
>
> 2016-05-19 14:03:31,210 [localhost-startStop-2] INFO
> org.springframework.b=
>
> oot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext-
> Closing=
> org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebAppli=
>
> cationContext@5e119034<mailto:
> org.springframework.boot.context.embedded.Ann<mailto:
> cationContext@5e119034
> %3cmailto:org.springframework.boot.context.embedded.Ann>=
>
> otationConfigEmbeddedWebApplicationContext@5e119034>: startup date [Thu
> May=
>
> 19 08:17:39 EDT 2016]; root of context hierarchy May 19, 2016 2:03:31 PM
> com.mongodb.util.management.jmx.JMXMBeanServer unre= gisterMBean
>
> WARNING: Unable to register MBean
> org.mongodb.driver:type=3DConnectionPool,=
>
> clusterId=3D1,host=3Dlocalhost,port=3D27017
>
> javax.management.InstanceNotFoundException:
> org.mongodb.driver:type=3DConne=
>
> ctionPool,clusterId=3D1,host=3Dlocalhost,port=3D27017
>
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(D=
>
> efaultMBeanServerInterceptor.java:1095)
>
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveU=
>
> nregisterMBean(DefaultMBeanServerInterceptor.java:427)
>
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregister=
>
> MBean(DefaultMBeanServerInterceptor.java:415)
>
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanS=
>
> erver.java:546)
>
> at
> com.mongodb.util.management.jmx.JMXMBeanServer.unregisterMBean(J=
>
> MXMBeanServer.java:52)
>
> at
> com.mongodb.JMXConnectionPoolListener.connectionPoolClosed(JMXCo=
>
> nnectionPoolListener.java:68)
>
> at
> com.mongodb.PooledConnectionProvider.close(PooledConnectionProvi=
>
> der.java:107)
>
>
>
> Any kind of help is appreciated.
>
To get some free support please ask at users@tomcat.apache.org mailing list.
Also please update to latest version of Tomcat (8.0.35) and try again.
>
> Thanks
>
> Ambica.
>
>