]
Galder Zamarreno commented on HHH-5563:
---------------------------------------
I don't think the patch is correct. Clients should not be needing to make these
checks. It should be the CacheManager itself doing it, see
JndiInfinispanRegionFactory creates region with a stopped cache, if
region previously existed
---------------------------------------------------------------------------------------------
Key: HHH-5563
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5563
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2)
Affects Versions: 3.5.5, 3.6.0.Beta4
Reporter: Paul Ferraro
Assignee: Galder Zamarreno
Attachments: patch.txt
Using JndiInfinispanRegionFactory, closing a hibernate session factory triggers the
destruction of all associated cache regions and stops the backing caches, though not the
cache manager itself (Due to HHH-5512). If the session factory is restarted (e.g. the
same application is redeployed), CacheManager.getCache(...) will return the already
existing cache, but with a TERMINATED status. Consequently, when determining the cache
instance for a given region, the region factory must always validate the status of the
cache, starting it if necessary.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: