LUDOVIC BOUE created POOL-291:
---------------------------------
Summary: failed to stop thread named [commons-pool-EvictionTimer]
Key: POOL-291
URL: https://issues.apache.org/jira/browse/POOL-291
Project: Commons Pool
Issue Type: Bug
Affects Versions: 2.0
Environment: Centos6 JDK1.7.0_71
Reporter: LUDOVIC BOUE
Priority: Minor
Hello,
I facing an issue when I stop my tomcat application that uses the Jedis
library. Do you have an idea of what cause the issue ? This is linked to the
thread commons-pool-EvictionTimer.
{code}
INFOS: A valid shutdown command was received via the shutdown port. Stopping
the Server instance.
mars 26, 2015 9:30:53 AM org.apache.coyote.AbstractProtocol pause
INFOS: Pausing ProtocolHandler ["http-bio-8181"]
mars 26, 2015 9:30:53 AM org.apache.catalina.core.StandardService stopInternal
INFOS: ArrĂȘt du service Catalina
mars 26, 2015 9:30:54 AM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
GRAVE: The web application [/myapp-ws] appears to have started a thread named
[commons-pool-EvictionTimer] but has failed to stop it. This is very likely to
create a memory leak.
mars 26, 2015 9:30:54 AM
org.springframework.web.context.support.XmlWebApplicationContext doClose
INFOS: Closing Root WebApplicationContext: startup date [Tue Mar 17 11:27:13
CET 2015]; root of context hierarchy
mars 26, 2015 9:30:54 AM
org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean destroy
INFOS: Closing JPA EntityManagerFactory for persistence unit
'afone-myapp-persist'
mars 26, 2015 9:30:54 AM org.apache.catalina.loader.WebappClassLoader
clearReferencesThreads
GRAVE: The web application [/myapp-jobs] appears to have started a thread named
[commons-pool-EvictionTimer] but has failed to stop it. This is very likely to
create a memory leak.
mars 26, 2015 9:30:54 AM org.apache.coyote.AbstractProtocol stop
INFOS: Stopping ProtocolHandler ["http-bio-8181"]
mars 26, 2015 9:30:54 AM org.apache.coyote.AbstractProtocol destroy
INFOS: Destroying ProtocolHandler ["http-bio-8181"]
{code}
Regards,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)