You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2012/12/05 09:22:58 UTC
[jira] [Created] (OWB-733) CLONE - ClassLoader leak in
WebBeansUtil.isScopeTypeNormalCache
Mark Struberg created OWB-733:
---------------------------------
Summary: CLONE - ClassLoader leak in WebBeansUtil.isScopeTypeNormalCache
Key: OWB-733
URL: https://issues.apache.org/jira/browse/OWB-733
Project: OpenWebBeans
Issue Type: Bug
Components: Context and Scopes
Affects Versions: 1.1.6
Reporter: chunlinyao
OpenWebBeans can shipped with JavaEE server(ex. TomEE), and codi may be in the WEB-INF/lib folder.
WebBeansUtil.isScopeTypeNormalCache will holder some annotation class like ViewAccessScope. This will cause classLoader leak when reload the web apps.
Maybe we should use weak reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OWB-733) CLONE - ClassLoader leak in
WebBeansUtil.isScopeTypeNormalCache
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg updated OWB-733:
------------------------------
Description:
OpenWebBeans can shipped with JavaEE server(ex. TomEE), and codi may be in the WEB-INF/lib folder.
WebBeansUtil.isScopeTypeNormalCache will holder some annotation class like ViewAccessScope. This will cause classLoader leak when reload the web apps.
Maybe we should use weak reference.
This also needs fixing in OWB-1.2.x
was:
OpenWebBeans can shipped with JavaEE server(ex. TomEE), and codi may be in the WEB-INF/lib folder.
WebBeansUtil.isScopeTypeNormalCache will holder some annotation class like ViewAccessScope. This will cause classLoader leak when reload the web apps.
Maybe we should use weak reference.
Affects Version/s: (was: 1.1.6)
1.2.0
Fix Version/s: 1.2.0
> CLONE - ClassLoader leak in WebBeansUtil.isScopeTypeNormalCache
> ---------------------------------------------------------------
>
> Key: OWB-733
> URL: https://issues.apache.org/jira/browse/OWB-733
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Context and Scopes
> Affects Versions: 1.2.0
> Reporter: chunlinyao
> Assignee: Mark Struberg
> Labels: leak
> Fix For: 1.2.0
>
>
> OpenWebBeans can shipped with JavaEE server(ex. TomEE), and codi may be in the WEB-INF/lib folder.
> WebBeansUtil.isScopeTypeNormalCache will holder some annotation class like ViewAccessScope. This will cause classLoader leak when reload the web apps.
> Maybe we should use weak reference.
> This also needs fixing in OWB-1.2.x
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OWB-733) CLONE - ClassLoader leak in
WebBeansUtil.isScopeTypeNormalCache
Posted by "Mark Struberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OWB-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg reassigned OWB-733:
---------------------------------
Assignee: Mark Struberg
> CLONE - ClassLoader leak in WebBeansUtil.isScopeTypeNormalCache
> ---------------------------------------------------------------
>
> Key: OWB-733
> URL: https://issues.apache.org/jira/browse/OWB-733
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Context and Scopes
> Affects Versions: 1.1.6
> Reporter: chunlinyao
> Assignee: Mark Struberg
> Labels: leak
>
> OpenWebBeans can shipped with JavaEE server(ex. TomEE), and codi may be in the WEB-INF/lib folder.
> WebBeansUtil.isScopeTypeNormalCache will holder some annotation class like ViewAccessScope. This will cause classLoader leak when reload the web apps.
> Maybe we should use weak reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira