You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2011/02/01 13:26:29 UTC
[jira] Updated: (AXIOM-354) Potential class loader leak caused by
the thread local in org.apache.axiom.util.UIDGenerator
[ https://issues.apache.org/jira/browse/AXIOM-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIOM-354:
----------------------------------
Fix Version/s: 1.2.12
> Potential class loader leak caused by the thread local in org.apache.axiom.util.UIDGenerator
> --------------------------------------------------------------------------------------------
>
> Key: AXIOM-354
> URL: https://issues.apache.org/jira/browse/AXIOM-354
> Project: Axiom
> Issue Type: Bug
> Components: API
> Affects Versions: 1.2.10
> Reporter: Andreas Veithen
> Fix For: 1.2.12
>
>
> UIDGenerator uses a ThreadLocal with a value class that belongs to Axiom (namely UIDGeneratorImpl). Since the ThreadLocal is never cleaned up explicitly (doing that would break the UIDGenerator), this may cause a class loader leak (i.e. in a Web application, it may prevent the class loader from being garbage collected when the application is stopped). Since UIDGeneratorImpl basically stores 3 values of type long, it should be easy to refactor the code so that the value class ThreadLocal is not loaded from the application class loader (e.g. by using long[] as value class). However, I first need to confirm that there is really a class loader leak here.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org