Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7AAC61727B for ; Mon, 30 Mar 2015 17:25:09 +0000 (UTC) Received: (qmail 96281 invoked by uid 500); 30 Mar 2015 17:24:53 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 96194 invoked by uid 500); 30 Mar 2015 17:24:53 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 96179 invoked by uid 99); 30 Mar 2015 17:24:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Mar 2015 17:24:53 +0000 Date: Mon, 30 Mar 2015 17:24:53 +0000 (UTC) From: "Mark Thomas (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (POOL-291) Failed to stop thread named [commons-pool-EvictionTimer] MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/POOL-291?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Thomas resolved POOL-291. ------------------------------ Resolution: Invalid The Pool needs to be closed when it is no longer used. You can use a Servle= tContextListener to do this. If you created the Pool, you need to close it.= If a 3rd party library created the Pool then it needs to close it and it s= hould provide you with an appropriate method to call to do so. > 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, 2.3 > 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 l= ibrary. 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. Stopp= ing 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 stopInt= ernal > INFOS: Arr=C3=AAt du service Catalina > mars 26, 2015 9:30:54 AM org.apache.catalina.loader.WebappClassLoader cle= arReferencesThreads > GRAVE: The web application [/myapp-ws] appears to have started a thread n= amed [commons-pool-EvictionTimer] but has failed to stop it. This is very l= ikely to create a memory leak. > mars 26, 2015 9:30:54 AM org.springframework.web.context.support.XmlWebAp= plicationContext 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.LocalContainerEntity= ManagerFactoryBean destroy > INFOS: Closing JPA EntityManagerFactory for persistence unit 'afone-myapp= -persist' > mars 26, 2015 9:30:54 AM org.apache.catalina.loader.WebappClassLoader cle= arReferencesThreads > 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)