[
https://issues.apache.org/jira/browse/MYFACES-2832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Concini resolved MYFACES-2832.
--------------------------------------
Fix Version/s: 1.2.10-SNAPSHOT
2.0.2-SNAPSHOT
Resolution: Fixed
> fix for potential classloader leaks from commons components
> -----------------------------------------------------------
>
> Key: MYFACES-2832
> URL: https://issues.apache.org/jira/browse/MYFACES-2832
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 1.2.0, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8,
> 1.2.9, 2.0.0, 2.0.1
> Reporter: Michael Concini
> Assignee: Michael Concini
> Fix For: 1.2.10-SNAPSHOT, 2.0.2-SNAPSHOT
>
>
> There are two potential places that MyFaces can leak classloaders when
> applications are undeployed/redeployed or restarted when used with some
> component libraries (e.g. Facelets 1.1.x).
> The first is due to a known leak in commons-beanutils
> (https://issues.apache.org/jira/browse/BEANUTILS-156). This is easily
> resolved by moving up to the most recent beanutils release. Will update the
> dependency in the pom.xml.
> The second is due to the EnvironmentCache in commons-discovery. In our
> LifecycleProviderFactory class, we currently execute
> DiscoverSingleton.find(), which under the covers puts an entry into the
> EnvironmentCache map. In some cases this map is preventing the classloader
> from being released. This can be resolved by calling
> DiscoverSingleton.release() when the servlet context is destroyed to make
> sure the cache gets cleared when an application is stopping.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
