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 211B318F57 for ; Tue, 15 Mar 2016 14:16:36 +0000 (UTC) Received: (qmail 7426 invoked by uid 500); 15 Mar 2016 14:16:35 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 7246 invoked by uid 500); 15 Mar 2016 14:16:34 -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 6985 invoked by uid 99); 15 Mar 2016 14:16:34 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Mar 2016 14:16:34 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8BED12C1F60 for ; Tue, 15 Mar 2016 14:16:33 +0000 (UTC) Date: Tue, 15 Mar 2016 14:16:33 +0000 (UTC) From: "Mark Thomas (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (POOL-308) JMX pool entries are never deregistered when web application unloads/reloads MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/POOL-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Thomas resolved POOL-308. ------------------------------ Resolution: Invalid You need to close the pool to release the resources. The released resources include the JMX registration. ServletContextListener.destroy() is typically where you'd do this. > JMX pool entries are never deregistered when web application unloads/reloads > ---------------------------------------------------------------------------- > > Key: POOL-308 > URL: https://issues.apache.org/jira/browse/POOL-308 > Project: Commons Pool > Issue Type: Bug > Affects Versions: 2.4.1, 2.4.2 > Reporter: Dmitri Blinov > > My web application contains commons-pool.jar inside WEB-INF/lib if that matters and runs on Tomcat7. > Each time application reloads without server restart, I see via JConsole on MBeans tab, that under org.apache.commons.pool2/GenericObjectPool node a list of created pools (pool, pool1, pool2 etc) is extended with newly created ones but old pool entries are never removed. > Besides the pools list starting look ugly and messy after a few restarts I beleive this may lead to memory leaks somehow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)