hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From krish_571 <krish_...@yahoo.com>
Subject Hbase memory leak error message when stopping tomcat
Date Mon, 07 Jul 2014 18:34:11 GMT
We have a java application (on tomcat) that connects to Hbase. We are getting
the below errors when we stop tomcat. Any thoughts?


SEVERE: The web application [/testapp] appears to have started a thread
named [hbase-tablepool-168-thread-1] but has failed to stop it. This is very
likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [hbase-tablepool-169-thread-1] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [IPC Client (47) connection to
ip-XX-XX-XX-XX.ec2.internal/XX-XX-XX-XX:60020 from tomcat] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [IPC Client (47) connection to
ip-XX-XX-XX-XX.ec2.internal/XX-XX-XX-XX:60020 from tomcat] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [IPC Client (47) connection to
ip-XX-XX-XX-XX.ec2.internal/XX-XX-XX-XX:60020 from tomcat] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [IPC Client (47) connection to
ip-XX-XX-XX-XX.ec2.internal/XX-XX-XX-XX:60020 from tomcat] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads SEVERE: The web application [/testapp] appears to
have started a thread named [hbase-tablepool-170-thread-1] but has failed to
stop it. This is very likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
checkThreadLocalMapForLeaks SEVERE: The web application [/testapp] created a
ThreadLocal with key of type [org.apache.hadoop.io.Text$1] (value
[org.apache.hadoop.io.Text$1@1dba6717]) and a value of type
[sun.nio.cs.UTF_8.Encoder] (value [sun.nio.cs.UTF_8$Encoder@38c62640]) but
failed to remove it when the web application was stopped. This is very
likely to create a memory leak.

Jul 07, 2014 2:51:38 PM org.apache.catalina.loader.WebappClassLoader
checkThreadLocalMapForLeaks

SEVERE: The web application [/testapp] created a ThreadLocal with key of
type [org.apache.hadoop.io.Text$1] (value
[org.apache.hadoop.io.Text$1@1dba6717]) and a value of type
[sun.nio.cs.UTF_8.Encoder] (value [sun.nio.cs.UTF_8$Encoder@58f950de]) but
failed to remove it when the web application was stopped. This is very
likely to create a memory leak.

Jul 07, 2014 2:51:39 PM org.apache.coyote.http11.Http11Protocol destroy
INFO: Stopping Coyote HTTP/1.1 on http-8080



--
View this message in context: http://apache-hbase.679495.n3.nabble.com/Hbase-memory-leak-error-message-when-stopping-tomcat-tp4061077.html
Sent from the HBase User mailing list archive at Nabble.com.

Mime
View raw message