[
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)
