You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hbase.apache.org by krish_571 <kr...@yahoo.com> on 2014/07/07 20:34:11 UTC
Hbase memory leak error message when stopping tomcat
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.
RE: Hbase memory leak error message when stopping tomcat
Posted by Vladimir Rodionov <vr...@carrieriq.com>.
HBase client spawns multiple threads inside Java application server (Tomcat). Tomcat does not like it.
No memory leaks - just warnings.
Best regards,
Vladimir Rodionov
Principal Platform Engineer
Carrier IQ, www.carrieriq.com
e-mail: vrodionov@carrieriq.com
________________________________________
From: krish_571 [krish_571@yahoo.com]
Sent: Monday, July 07, 2014 11:34 AM
To: user@hbase.apache.org
Subject: Hbase memory leak error message when stopping tomcat
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.
Confidentiality Notice: The information contained in this message, including any attachments hereto, may be confidential and is intended to be read only by the individual or entity to whom this message is addressed. If the reader of this message is not the intended recipient or an agent or designee of the intended recipient, please note that any review, use, disclosure or distribution of this message or its attachments, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Notifications@carrieriq.com and delete or destroy any copy of this message and its attachments.