You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jason Pell (JIRA)" <ji...@apache.org> on 2012/10/17 02:02:02 UTC
[jira] [Created] (CXF-4577) Support EHCACHE 2.5.2+
Jason Pell created CXF-4577:
-------------------------------
Summary: Support EHCACHE 2.5.2+
Key: CXF-4577
URL: https://issues.apache.org/jira/browse/CXF-4577
Project: CXF
Issue Type: Improvement
Components: JAX-WS Runtime
Affects Versions: 2.7.0
Reporter: Jason Pell
Priority: Minor
Attachments: EhCacheIssue.tar.gz
Upgrading ehcache to 2.5.2 causes some unexpected issues when using ws-security timestamp ehcache and / or nonce caches. Due to an api change in 2.5.2 when destroying an endpoint the global ehcache CacheManager is also shutdown.
I am attaching a project which demonstrates the issue. I will be working on a fix for the issue so we can upgrade to 2.5.2. The fix will be backwards compatible to 2.5.1
--
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] (CXF-4577) Support EHCACHE 2.5.2+
Posted by "Jason Pell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CXF-4577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Pell updated CXF-4577:
----------------------------
Attachment: EhCacheIssue.tar.gz
Run the test case and you will see that the globally defined CacheManager (defined using EhCacheManagerFactoryBean and shared=true) is shut down when a cxf endpoint which has a ehcache is destroyed.
> Support EHCACHE 2.5.2+
> -----------------------
>
> Key: CXF-4577
> URL: https://issues.apache.org/jira/browse/CXF-4577
> Project: CXF
> Issue Type: Improvement
> Components: JAX-WS Runtime
> Affects Versions: 2.7.0
> Reporter: Jason Pell
> Priority: Minor
> Attachments: EhCacheIssue.tar.gz
>
>
> Upgrading ehcache to 2.5.2 causes some unexpected issues when using ws-security timestamp ehcache and / or nonce caches. Due to an api change in 2.5.2 when destroying an endpoint the global ehcache CacheManager is also shutdown.
> I am attaching a project which demonstrates the issue. I will be working on a fix for the issue so we can upgrade to 2.5.2. The fix will be backwards compatible to 2.5.1
--
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