May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9016) Component metadata serialization format changes depending on compiler

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9016?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9016: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/6022 (was: https://github.com/infinispan/infinispan/pull/5881) > Component metadata serialization format changes depending on compiler > --------------------------------------------------------------------- > > Key: ISPN-9016 > URL: https://issues.jboss.org/browse/ISPN-9016 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Fix For: 9.3.0.CR1 > > > The field and method metadata classes have a {{serialVersionUUID}}, but {{ComponentMetadata}} itself doesn't have it, so it can change at any time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9219) WeakCounterAPITest.testAdd random failures

by Dan Berindei (JIRA)

Dan Berindei created ISPN-9219: ---------------------------------- Summary: WeakCounterAPITest.testAdd random failures Key: ISPN-9219 URL: https://issues.jboss.org/browse/ISPN-9219 Project: Infinispan Issue Type: Bug Components: Clustered Counter Affects Versions: 9.3.0.Beta1 Reporter: Dan Berindei Assignee: Pedro Ruivo Priority: Critical Fix For: 9.3.0.Final The exact assertion message and stack trace varies: {noformat} java.lang.AssertionError: expected:<0> but was:<-40> java.lang.AssertionError: expected:<0> but was:<-20> at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:62) at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:27) at org.infinispan.server.hotrod.counter.impl.BaseCounterImplTest.testAdd(BaseCounterImplTest.java:68) at org.infinispan.client.hotrod.counter.WeakCounterAPITest.testAdd(WeakCounterAPITest.java:31) java.lang.AssertionError: expected:<20> but was:<40> java.lang.AssertionError: expected:<20> but was:<30> at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:62) at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:27) at org.infinispan.server.hotrod.counter.impl.BaseCounterImplTest.testAdd(BaseCounterImplTest.java:65) at org.infinispan.client.hotrod.counter.WeakCounterAPITest.testAdd(WeakCounterAPITest.java:31) {noformat} https://ci.infinispan.org/job/Infinispan/job/master/630/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9219) WeakCounterAPITest.testAdd random failures

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9219?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9219: ------------------------------- Status: Open (was: New) > WeakCounterAPITest.testAdd random failures > ------------------------------------------ > > Key: ISPN-9219 > URL: https://issues.jboss.org/browse/ISPN-9219 > Project: Infinispan > Issue Type: Bug > Components: Clustered Counter > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Labels: testsuite_stability > Fix For: 9.3.0.Final > > > The exact assertion message and stack trace varies: > {noformat} > java.lang.AssertionError: expected:<0> but was:<-40> > java.lang.AssertionError: expected:<0> but was:<-20> > at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:62) > at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:27) > at org.infinispan.server.hotrod.counter.impl.BaseCounterImplTest.testAdd(BaseCounterImplTest.java:68) > at org.infinispan.client.hotrod.counter.WeakCounterAPITest.testAdd(WeakCounterAPITest.java:31) > java.lang.AssertionError: expected:<20> but was:<40> > java.lang.AssertionError: expected:<20> but was:<30> > at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:62) > at org.infinispan.server.hotrod.counter.impl.WeakCounterImplTestStrategy.assertCounterValue(WeakCounterImplTestStrategy.java:27) > at org.infinispan.server.hotrod.counter.impl.BaseCounterImplTest.testAdd(BaseCounterImplTest.java:65) > at org.infinispan.client.hotrod.counter.WeakCounterAPITest.testAdd(WeakCounterAPITest.java:31) > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/630/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8894) Remove usages of junit.framework.*

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8894?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8894: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.CR1 Resolution: Done > Remove usages of junit.framework.* > ---------------------------------- > > Key: ISPN-8894 > URL: https://issues.jboss.org/browse/ISPN-8894 > Project: Infinispan > Issue Type: Enhancement > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Minor > Fix For: 9.3.0.CR1, 9.3.0.Final > > > Please stop using it; use org.junit.* instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9173) Availability mode should be updated atomically with the actual members

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-9173?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9173: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6021 > Availability mode should be updated atomically with the actual members > ---------------------------------------------------------------------- > > Key: ISPN-9173 > URL: https://issues.jboss.org/browse/ISPN-9173 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.0.Beta1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.3.0.CR1 > > > This is a follow-up on ISPN-7682, which asks for the topology itself to be updated atomically. > {{LocalTopologyManagerImpl}} has additional logic to update the availability mode first when the cache becomes degraded and to update it last when the cache becomes available, which means any delay between the updates cannot cause data inconsistencies. > But that logic doesn't really belong in {{LocalTopologyManagerImpl}}, and it's easy to forget it's there (and in fact we had a bug there related to the new rebalance phases). > In addition, tests that want to check the cache behaviour in degraded mode and wait only for the availability mode change will fail if there's a big delay between the availability mode change. I actually hit this while testing my ISPN-8731/ISPN-7682 changes, and I had added a random delay in {{StateConsumerImpl}} before {{distributionManager.setCacheTopology()}}. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9218) Hot Rod client should wrap InterruptedException in HotRodClientException

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9218: -------------------------------------- Summary: Hot Rod client should wrap InterruptedException in HotRodClientException Key: ISPN-9218 URL: https://issues.jboss.org/browse/ISPN-9218 Project: Infinispan Issue Type: Bug Reporter: Galder Zamarreño Since this is a client-level exception. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9217) Interrupted thread should result in InterruptedException being sent back

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-9217: -------------------------------------- Summary: Interrupted thread should result in InterruptedException being sent back Key: ISPN-9217 URL: https://issues.jboss.org/browse/ISPN-9217 Project: Infinispan Issue Type: Bug Components: Remote Protocols Affects Versions: 9.1.7.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 9.1.8.Final If a pre-netty Hot Rod client gets interrupted, it will result in an IllegalStateException. This is because finding an interrupted thread returns a negative value, which RetryOnFailureOperation will result in not retrying and throwing IllegalStateException (see [here|https://github.com/infinispan/infinispan/blob/9.1.x/client/hotrod-cl...] and [here|https://github.com/infinispan/infinispan/blob/9.1.x/client/hotrod-cl...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9214) JBossStandaloneJTAManagerLookup is using deprecated integration names

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ISPN-9214?page=com.atlassian.jira.plugin.... ] David Lloyd commented on ISPN-9214: ----------------------------------- I would recommend adding a WildFly strategy (which would be used with WildFly 11 and later) which references {{ContextTransactionManager}} and {{LocalUserTransaction}} instead of the Narayana/Arjuna classes. The existing JBoss strategy would continue to work for JBoss AS 7 and earlier, and WildFly 8, 9, and 10. The JNDI name has not changed. > JBossStandaloneJTAManagerLookup is using deprecated integration names > --------------------------------------------------------------------- > > Key: ISPN-9214 > URL: https://issues.jboss.org/browse/ISPN-9214 > Project: Infinispan > Issue Type: Task > Components: Core, Integration > Reporter: Sanne Grinovero > Assignee: Scott Marlow > Priority: Minor > > Scott changed the Hibernate ORM {{JBossStandaloneJTAManagerLookup}}, as on WildFly 13+, JTA client code that directly references the {{com.arjuna.ats.jta.TransactionManager}}, needs to instead use the WildFly Transaction Client, or it may see incorrect TX status. > I assume the Infinispan standalone client will need to be updated as well. > See: > - https://hibernate.atlassian.net/browse/HHH-12640 > - https://hibernate.atlassian.net/browse/HHH-12620 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9194) EntityRegionAccessStrategyTest.testRemoveAll failing randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9194?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-9194: ---------------------------------------- This seems to be a case of a previous put lingering around and causing an expecting interceptor to succeed in a later test. Attached TRACE logs with more information, but it's not yet fully clear what the origin of this put is and how to make sure it gets consumed before moving on to the next test. > EntityRegionAccessStrategyTest.testRemoveAll failing randomly > ------------------------------------------------------------- > > Key: ISPN-9194 > URL: https://issues.jboss.org/browse/ISPN-9194 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.CR1, 9.3.0.Final > > Attachments: ispn9194-log-v3.tgz, ispn9194-log-v4.tgz > > > {code} > [INFO] Running org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] Tests run: 153, Failures: 1, Errors: 0, Skipped: 17, Time elapsed: 23.447 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] testRemoveAll[JTA, REPL_SYNC, AccessType[read-only]](org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest) Time elapsed: 0.01 s <<< FAILURE! > java.lang.AssertionError: expected:<VALUE1/1> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.evictOrRemoveAllTest(AbstractRegionAccessStrategyTest.java:490) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.testRemoveAll(AbstractRegionAccessStrategyTest.java:433) > 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:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9194) EntityRegionAccessStrategyTest.testRemoveAll failing randomly

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-9194?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9194: ----------------------------------- Attachment: ispn9194-log-v4.tgz > EntityRegionAccessStrategyTest.testRemoveAll failing randomly > ------------------------------------------------------------- > > Key: ISPN-9194 > URL: https://issues.jboss.org/browse/ISPN-9194 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.3.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.3.0.CR1, 9.3.0.Final > > Attachments: ispn9194-log-v3.tgz, ispn9194-log-v4.tgz > > > {code} > [INFO] Running org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] Tests run: 153, Failures: 1, Errors: 0, Skipped: 17, Time elapsed: 23.447 s <<< FAILURE! - in org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest > [ERROR] testRemoveAll[JTA, REPL_SYNC, AccessType[read-only]](org.infinispan.test.hibernate.cache.commons.entity.EntityRegionAccessStrategyTest) Time elapsed: 0.01 s <<< FAILURE! > java.lang.AssertionError: expected:<VALUE1/1> but was:<null> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:834) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:144) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.evictOrRemoveAllTest(AbstractRegionAccessStrategyTest.java:490) > at org.infinispan.test.hibernate.cache.commons.AbstractRegionAccessStrategyTest.testRemoveAll(AbstractRegionAccessStrategyTest.java:433) > 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:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.hibernate.testing.junit4.ExtendedFrameworkMethod.invokeExplosively(ExtendedFrameworkMethod.java:45) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.lang.Thread.run(Thread.java:748) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2018