October 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5854) NonTxInvalidationInterceptor added twice to cache used for Hibernate 2LC

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-5854?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-5854: ----------------------------------- This is a Hibernate bug, so you should raise JIRA in https://hibernate.atlassian.net rather than for Infinispan. You say that you use the same cache for multiple entities - although you configure single 'entities' cache, this becomes rather a template configuration for the caches which are per-entity-hierarchy. Do you really share the cache for different entities? Could you attach your persistence.xml and infinispan config to the JIRA? It is possible to create the PutFromLoadValidator twice for the same cache only when you have two different regions mapped to the same cache, which is not a legal configuration. > NonTxInvalidationInterceptor added twice to cache used for Hibernate 2LC > ------------------------------------------------------------------------ > > Key: ISPN-5854 > URL: https://issues.jboss.org/browse/ISPN-5854 > Project: Infinispan > Issue Type: Bug > Components: Integration > Affects Versions: 7.2.5.Final > Reporter: Karl von Randow > Assignee: Galder Zamarreño > > I use the same Infinispan cache for multiple Hibernate entities. The {{PutFromLoadValidator}} looks for and replaces the {{InvalidationInterceptor}} the first time it sees the cache, but the second time it fails to find the {{InvalidationInterceptor}} and ends up with {{invalidationPosition = 0}} from line 168, which means it incorrectly removes the first interceptor from the chain and then tries to add the {{NonTxInvalidationInterceptor}} again, causing the exception below. > Perhaps the {{NonTxInvalidationInterceptor}} should only be added once per cache, or the {{accessStrategy}} should be cached or something? > {noformat} > org.infinispan.commons.CacheConfigurationException: Detected interceptor of type [org.hibernate.cache.infinispan.access.NonTxInvalidationInterceptor] being added to the interceptor chain 170588969 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:883) > at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:192) > at org.hibernate.cache.infinispan.access.PutFromLoadValidator.<init>(PutFromLoadValidator.java:133) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.prepareForValidation(BaseTransactionalDataRegion.java:137) > at org.hibernate.cache.infinispan.impl.BaseTransactionalDataRegion.createAccessDelegate(BaseTransactionalDataRegion.java:122) > at org.hibernate.cache.infinispan.collection.CollectionRegionImpl.buildAccessStrategy(CollectionRegionImpl.java:49) > at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:400) > at org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444) > at org.hibernate.boot.internal.MetadataImpl.buildSessionFactory(MetadataImpl.java:170) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5863) Expiration does not work correct in C/S mode for a cache if putIfAbsent(K, V) is used

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ] Work on ISPN-5863 started by Galder Zamarreño. ---------------------------------------------- > Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) is used > ------------------------------------------------------------------------------------ > > Key: ISPN-5863 > URL: https://issues.jboss.org/browse/ISPN-5863 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > > If the ISPN server cache is configured with expiration like: > <cache-container name="local" default-cache="default" statistics="true"> > <state-persistence/> > <local-cache name="default" start="EAGER"> > <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/> > <transaction mode="NONE"/> > <expiration lifespan="1000" interval="20000"/> > </local-cache> > The entry should automatic expired in 1second after it is added. > But a client still have the key > - after 1 sec where it should have been expired > - after 20 sec where the reaper should have removed it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5863) Expiration does not work correct in C/S mode for a cache if putIfAbsent(K, V) is used

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-5863: ----------------------------------- Status: Open (was: New) > Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) is used > ------------------------------------------------------------------------------------ > > Key: ISPN-5863 > URL: https://issues.jboss.org/browse/ISPN-5863 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > > If the ISPN server cache is configured with expiration like: > <cache-container name="local" default-cache="default" statistics="true"> > <state-persistence/> > <local-cache name="default" start="EAGER"> > <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/> > <transaction mode="NONE"/> > <expiration lifespan="1000" interval="20000"/> > </local-cache> > The entry should automatic expired in 1second after it is added. > But a client still have the key > - after 1 sec where it should have been expired > - after 20 sec where the reaper should have removed it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5863) Expiration does not work correct in C/S mode for a cache if putIfAbsent(K, V) is used

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-5863?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-5863: -------------------------------------- Assignee: Galder Zamarreño > Expiration does not work correct in C/S mode for a cache if putIfAbsent(K,V) is used > ------------------------------------------------------------------------------------ > > Key: ISPN-5863 > URL: https://issues.jboss.org/browse/ISPN-5863 > Project: Infinispan > Issue Type: Bug > Affects Versions: 8.1.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > > If the ISPN server cache is configured with expiration like: > <cache-container name="local" default-cache="default" statistics="true"> > <state-persistence/> > <local-cache name="default" start="EAGER"> > <locking acquire-timeout="30000" concurrency-level="1000" striping="false"/> > <transaction mode="NONE"/> > <expiration lifespan="1000" interval="20000"/> > </local-cache> > The entry should automatic expired in 1second after it is added. > But a client still have the key > - after 1 sec where it should have been expired > - after 20 sec where the reaper should have removed it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5530) AtomicObjectFactoryTest.distributedCacheTest random failures

by Antoine Toulme (JIRA)

[ https://issues.jboss.org/browse/ISPN-5530?page=com.atlassian.jira.plugin.... ] Antoine Toulme commented on ISPN-5530: -------------------------------------- See here my commit to try to invoke all futures at once: https://github.com/atoulme/infinispan/commit/c255aa46885c9cdccb88bc6ea96d... I don't think it's worth a pull request, since it fixes nothing. Let me know if that helps you if you can reproduce better from your end? > AtomicObjectFactoryTest.distributedCacheTest random failures > ------------------------------------------------------------ > > Key: ISPN-5530 > URL: https://issues.jboss.org/browse/ISPN-5530 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.1.0.Final > > > {noformat} > java.lang.AssertionError: obtained = 999; espected = 1000 expected:<1000> but was:<999> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.infinispan.atomic.AtomicObjectFactoryTest.distributedCacheTest(AtomicObjectFactoryTest.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5530) AtomicObjectFactoryTest.distributedCacheTest random failures

by Antoine Toulme (JIRA)

[ https://issues.jboss.org/browse/ISPN-5530?page=com.atlassian.jira.plugin.... ] Antoine Toulme commented on ISPN-5530: -------------------------------------- I ran the test 100 times with the latest master, without reproducing the issue. I took it a notch further by modifying the code ever so slightly. I tried to increase the number of managers (NCACHES) and calls (NCALLS). I still could not reproduce the problem. > AtomicObjectFactoryTest.distributedCacheTest random failures > ------------------------------------------------------------ > > Key: ISPN-5530 > URL: https://issues.jboss.org/browse/ISPN-5530 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.1.0.Final > > > {noformat} > java.lang.AssertionError: obtained = 999; espected = 1000 expected:<1000> but was:<999> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) > at org.infinispan.atomic.AtomicObjectFactoryTest.distributedCacheTest(AtomicObjectFactoryTest.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:714) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:348) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:38) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:382) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5871) FlagsEnabledTest.testWithFlagsSemantics always fails

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5871?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5871: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3766 > FlagsEnabledTest.testWithFlagsSemantics always fails > ---------------------------------------------------- > > Key: ISPN-5871 > URL: https://issues.jboss.org/browse/ISPN-5871 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.1.0.Alpha2 > > > The ISPN-5857 fix changed the way ReplicatedConsistentHash maps keys to segments. > FlagsEnabledTest assumes its string keys have a certain locality in order to test which cache loader is accessed, and the ReplicatedConsistentHash changes broke that assumption. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5871) FlagsEnabledTest.testWithFlagsSemantics always fails

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5871?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5871: ------------------------------- Status: Open (was: New) > FlagsEnabledTest.testWithFlagsSemantics always fails > ---------------------------------------------------- > > Key: ISPN-5871 > URL: https://issues.jboss.org/browse/ISPN-5871 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Labels: testsuite_stability > Fix For: 8.1.0.Alpha2 > > > The ISPN-5857 fix changed the way ReplicatedConsistentHash maps keys to segments. > FlagsEnabledTest assumes its string keys have a certain locality in order to test which cache loader is accessed, and the ReplicatedConsistentHash changes broke that assumption. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5871) FlagsEnabledTest.testWithFlagsSemantics always fails

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5871: ---------------------------------- Summary: FlagsEnabledTest.testWithFlagsSemantics always fails Key: ISPN-5871 URL: https://issues.jboss.org/browse/ISPN-5871 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Reporter: Dan Berindei Assignee: Dan Berindei Priority: Blocker Fix For: 8.1.0.Alpha2 The ISPN-5857 fix changed the way ReplicatedConsistentHash maps keys to segments. FlagsEnabledTest assumes its string keys have a certain locality in order to test which cache loader is accessed, and the ReplicatedConsistentHash changes broke that assumption. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5870) Expose query JPA string and parameters in the RemoteQuery

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-5870?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes deleted ISPN-5870: ------------------------------------ > Expose query JPA string and parameters in the RemoteQuery > --------------------------------------------------------- > > Key: ISPN-5870 > URL: https://issues.jboss.org/browse/ISPN-5870 > Project: Infinispan > Issue Type: Feature Request > Reporter: Gustavo Fernandes > > So that the query building blocks can be transmitted over the network -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2015