[jboss-jira] [JBoss JIRA] (WFLY-906) Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction
Scott Marlow (JIRA)
jira-events at lists.jboss.org
Mon Jul 8 18:04:20 EDT 2013
[ https://issues.jboss.org/browse/WFLY-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Marlow closed WFLY-906.
-----------------------------
> Hibernate/Infinispan 2nd Level Caches set to transaction-mode=NONE stop functioning after an explicit eviction
> --------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-906
> URL: https://issues.jboss.org/browse/WFLY-906
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Reporter: Fredrik Lagerblad
> Assignee: Scott Marlow
>
> The caches in the 'infinispan' subsystem configured with <transaction mode="NONE"/> get stuck in state= CLEARING when you perform a programmatic evict() on them to clear the caches. (Using e.g. em.getEntityManagerFactory().getCache().evictAll() )
>
> The problem seem to lie within the class 'org.hibernate.cache.infinispan.impl.BaseRegion, where the 'checkValid' method fails to clear the cache (and set back the state to VALID). The reason it fails is due to that it calls: cacheAdapter.withinTx() , which in turn tries to get the TransactionManager from the cache (which seems to be null for these non-transactional caches), and then NPEs on the tm.begin(); The NPE is caught and logs out "Could not invalidate region: null", and never set the state in VALID. So from thereon the caches are in an Invalid state and is not used anymore by Infinispan, thus leading to much performance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list