Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.7
-
None
-
Unknown
Description
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