You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2012/06/07 19:33:23 UTC
[jira] [Created] (CXF-4366) If not use WS-SecPolicy, ehcache caches
not cleaned up
Daniel Kulp created CXF-4366:
--------------------------------
Summary: If not use WS-SecPolicy, ehcache caches not cleaned up
Key: CXF-4366
URL: https://issues.apache.org/jira/browse/CXF-4366
Project: CXF
Issue Type: Bug
Components: WS-* Components
Affects Versions: 2.6.1, 2.5.4, 2.4.8
Reporter: Daniel Kulp
Assignee: Daniel Kulp
Fix For: 2.4.9, 2.5.5, 2.6.2
When using the ehcache based stores with manually configured WSS4J*Interceptors instead of WS-Policy based, the listeners that "close" the stores may not be registered and thus the stores will not get properly cleaned up locking the cache manager and consuming threads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4366) If not use WS-SecPolicy, ehcache
caches not cleaned up
Posted by "Daniel Kulp (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved CXF-4366.
------------------------------
Resolution: Fixed
> If not use WS-SecPolicy, ehcache caches not cleaned up
> ------------------------------------------------------
>
> Key: CXF-4366
> URL: https://issues.apache.org/jira/browse/CXF-4366
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.4.8, 2.5.4, 2.6.1
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: 2.4.9, 2.5.5, 2.6.2
>
>
> When using the ehcache based stores with manually configured WSS4J*Interceptors instead of WS-Policy based, the listeners that "close" the stores may not be registered and thus the stores will not get properly cleaned up locking the cache manager and consuming threads.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira