[jboss-jira] [JBoss JIRA] (WFLY-6283) CacheConfigurationException: Detected interceptor of type [org.hibernate.cache.infinispan.access.TxInvalidationInterceptor] being added to the interceptor chain 231985794 more than once!

[Madhusudana Sunnapu (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13343658#comment-13343658 ] 

Madhusudana Sunnapu edited comment on WFLY-6283 at 1/17/17 6:53 AM:
--------------------------------------------------------------------

I am using JBoss EAP 7.0.0 (latest). If I run the JBoss in standalone mode (full.xml or full-ha.xml) and deploy my jar file (that is using hibernate second-level cache) it gets deployed successfully. 

But when I deploy the same jar file on to the same JBoss when it is running in a managed server mode the above exception *(Detected interceptor of type [org.hibernate.cache.infinispan.access.TxInvalidationInterceptor] being added to the interceptor chain ... more than once!).* 

The profile I am using is "full-ha" in managed server mode.
The jar that I am deploying is same and JBoss EAP machine I am using is the same in both the cases.

That is where I am wondering and just wanted to confirm if this fix applies (and tested) for both standalone and managed server mode or only standalone mode.

____________________________________________________________________

UPDATE: It is working now even in the managed server mode. I believe I might have messed up some configuration earlier and when I did a fresh install of JBoss 7 and tried it, it started to work.


was (Author: madhusudanareddysunnapu):
I am using JBoss EAP 7.0.0 (latest). If I run the JBoss in standalone mode (full.xml or full-ha.xml) and deploy my jar file (that is using hibernate second-level cache) it gets deployed successfully. 

But when I deploy the same jar file on to the same JBoss when it is running in a managed server mode the above exception *(Detected interceptor of type [org.hibernate.cache.infinispan.access.TxInvalidationInterceptor] being added to the interceptor chain ... more than once!).* 

The profile I am using is "full-ha" in managed server mode.
The jar that I am deploying is same and JBoss EAP machine I am using is the same in both the cases.

That is where I am wondering and just wanted to confirm if this fix applies (and tested) for both standalone and managed server mode or only standalone mode.

> CacheConfigurationException: Detected interceptor of type [org.hibernate.cache.infinispan.access.TxInvalidationInterceptor] being added to the interceptor chain 231985794 more than once!
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-6283
>                 URL: https://issues.jboss.org/browse/WFLY-6283
>             Project: WildFly
>          Issue Type: Bug
>          Components: JPA / Hibernate
>    Affects Versions: 10.0.0.Final
>            Reporter: Harold Campbell
>            Assignee: Paul Ferraro
>             Fix For: 10.1.0.CR1, 10.1.0.Final
>
>
> With second level caching enabled in a persistence unit, my application can only be deployed once without restarting wildfly. Redeployment results in this stacktrace:
> 19:06:48,764 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 87) MSC000001: Failed to start service jboss.persistenceunit."winthorpe-ear.ear#winthorpedb": org.jboss.msc.service.StartException in service jboss.persistenceunit."winthorpe-ear.ear#winthorpedb": javax.persistence.PersistenceException: [PersistenceUnit: winthorpedb] Unable to build Hibernate SessionFactory
> 	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172)
> 	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:117)
> 	at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667)
> 	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:182)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> 	at org.jboss.threads.JBossThread.run(JBossThread.java:320)
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: winthorpedb] Unable to build Hibernate SessionFactory
> 	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:954)
> 	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:882)
> 	at org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> 	at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:154)
> 	... 7 more
> Caused by: org.infinispan.commons.CacheConfigurationException: Detected interceptor of type [org.hibernate.cache.infinispan.access.TxInvalidationInterceptor] being added to the interceptor chain 231985794 more than once!
> 	at org.infinispan.interceptors.InterceptorChain.assertNotAdded(InterceptorChain.java:76)
> 	at org.infinispan.interceptors.InterceptorChain.addInterceptor(InterceptorChain.java:90)
> 	at org.infinispan.cache.impl.CacheImpl.addInterceptor(CacheImpl.java:879)
> 	at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.addInterceptor(AbstractDelegatingAdvancedCache.java:65)
> 	at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:184)
> 	at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:133)
> 	at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.prepareForValidation(BaseTransactionalDataRegion.java:145)
> 	at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.createAccessDelegate(BaseTransactionalDataRegion.java:130)
> 	at org.hibernate.cache.infinispan.naturalid.NaturalIdRegionImpl.buildAccessStrategy(NaturalIdRegionImpl.java:50)
> 	at org.hibernate.internal.SessionFactoryImpl.determineNaturalIdRegionAccessStrategy(SessionFactoryImpl.java:600)
> 	at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:339)
> 	at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444)
> 	at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:879)
> 	... 9 more



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)