[jboss-jira] [JBoss JIRA] Reopened: (JBCLUSTER-249) CacheManager destroys caches when it stops

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBCLUSTER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry reopened JBCLUSTER-249:
----------------------------------------



> CacheManager destroys caches when it stops
> ------------------------------------------
>
>                 Key: JBCLUSTER-249
>                 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-249
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: HA-Server-Cache-JBC
>    Affects Versions: HA-Server-Cache-JBC 2.1.0.GA 
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: HA-Server-Cache-JBC 2.1.1.GA, HA-Server-Cache-JBC 2.0.2.Final 
>
>
> CacheManager.stop() destroys all running caches. This is incorrect; since it didn't create them in start(). It should just call releaseCache for all eager-start caches to reduce the ref count. Then make the releaseCache method usable after stop() so if anyone has a ref to the CacheManager they can still release the cache.
> This is essentially a workaround-type solution for JBAS-7228 and JBAS-7229. The correct solution for those is to have services using the CacheManager depend on it, so they stop first.  But the MC may not be aware of everything using CacheManager (e.g. a Hibernate SessionFactory created by a ServletContextListener) so it can't always enforce dependencies. And, the ^^^ behavior of stop only undoing what start did is correct anyway.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira