[
https://issues.apache.org/jira/browse/CXF-5802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047872#comment-14047872
]
Daniel Kulp commented on CXF-5802:
----------------------------------
The call to removeCache caused some issues on the client side where if you have
two client proxies, they would use the same cache, but if you close one of
them, the cache would be removed and the other client would then become
invalid. I've added a reference count to the cache that I hope fixes this.
> Share an existing global ehcache manager for ws security replay caches
> ----------------------------------------------------------------------
>
> Key: CXF-5802
> URL: https://issues.apache.org/jira/browse/CXF-5802
> Project: CXF
> Issue Type: Improvement
> Affects Versions: 2.7.11, 2.6.14, 3.0.0
> Reporter: Jason Pell
> Assignee: Jason Pell
> Fix For: 2.6.15, 2.7.12, 3.0.1
>
>
> In CXF if we are using ehcache for such as hibernate, cxf creates a separate
> ehcache manager. We can configure it to use the same ehcache.xml file, but
> still the additional manager is created.
> Enhance CXF to use a global ehcache manager, and a single ehcache.xml as
> configuration options.
> This will avoid the following errors in logs when CXF creates an additional
> manager when using a single ehcache.xml file
> net.sf.ehcache.DiskStorePathManager - diskStorePath '../tmp' is already used
> by an existing CacheManager either in the same VM or in a different process.
> The diskStore path for this CacheManager will be set to
> ../tmp/ehcache_auto_created2006383781232499638diskstore.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
