[hibernate-issues] [Hibernate-JIRA] Updated: (HHH-5563) JndiInfinispanRegionFactory creates region with a stopped cache, if region previously existed
Galder Zamarreno (JIRA)
noreply at atlassian.com
Thu Sep 16 13:05:22 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Galder Zamarreno updated HHH-5563:
----------------------------------
Affects Version/s: (was: 3.6.0.Beta4)
(was: 3.5.5)
3.5.6
3.6.0.CR1
Fix Version/s: 3.6.x
3.5.x
> 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.6, 3.6.0.CR1
> Reporter: Paul Ferraro
> Assignee: Galder Zamarreno
> Fix For: 3.5.x, 3.6.x
>
> 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: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list