August 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8114) Random failures in loading from Hibernate Cache

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8114?page=com.atlassian.jira.plugin.... ] Galder Zamarreño reassigned ISPN-8114: -------------------------------------- Assignee: Galder Zamarreño (was: Sebastian Łaskawiec) > Random failures in loading from Hibernate Cache > ----------------------------------------------- > > Key: ISPN-8114 > URL: https://issues.jboss.org/browse/ISPN-8114 > Project: Infinispan > Issue Type: Bug > Components: Hibernate Cache > Affects Versions: 9.1.0.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: testsuite_stability > Fix For: 9.1.1.Final > > > {{org.infinispan.test.hibernate.cache.functional.cluster.NaturalIdInvalidationTest.testAll[read-only, INVALIDATION_SYNC]}} > {{org.infinispan.test.hibernate.cache.functional.cluster.NaturalIdInvalidationTest.testAll[transactional, INVALIDATION_SYNC]}} > {code} > java.lang.AssertionError: Citizen (1234) should have present in the cache > at org.junit.Assert.fail(Assert.java:88) > at org.infinispan.test.hibernate.cache.functional.cluster.NaturalIdInvalidationTest.assertLoadedFromCache(NaturalIdInvalidationTest.java:144) > at org.infinispan.test.hibernate.cache.functional.cluster.NaturalIdInvalidationTest.testAll(NaturalIdInvalidationTest.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:498) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > 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$StatementThread.run(FailOnTimeout.java:74) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6842) ReplTotalOrderStateTransferFunctional1PcTest.testSTWithWritingTxThread random failures

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-6842?page=com.atlassian.jira.plugin.... ] Katia Aresti commented on ISPN-6842: ------------------------------------ This test seems deleted > ReplTotalOrderStateTransferFunctional1PcTest.testSTWithWritingTxThread random failures > -------------------------------------------------------------------------------------- > > Key: ISPN-6842 > URL: https://issues.jboss.org/browse/ISPN-6842 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.Alpha2 > Reporter: Dan Berindei > Labels: testsuite_stability > > It seems the commit fails and Infinispan rolls back the JTA transaction automatically. Then the test's rollback fails, hiding the initial exception: > {noformat} > java.util.concurrent.ExecutionException: java.lang.IllegalStateException: BaseTransaction.rollback - ARJUNA016074: no transaction! > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at org.infinispan.statetransfer.StateTransferFunctionalTest.writingThreadTest(StateTransferFunctionalTest.java:353) > at org.infinispan.statetransfer.StateTransferFunctionalTest.testSTWithWritingTxThread(StateTransferFunctionalTest.java:251) > Caused by: java.lang.IllegalStateException: BaseTransaction.rollback - ARJUNA016074: no transaction! > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.rollback(BaseTransaction.java:139) > at org.infinispan.statetransfer.StateTransferFunctionalTest$WritingTask.call(StateTransferFunctionalTest.java:140) > at org.infinispan.statetransfer.StateTransferFunctionalTest$WritingTask.call(StateTransferFunctionalTest.java:106) > at org.infinispan.test.AbstractInfinispanTest$LoggingCallable.call(AbstractInfinispanTest.java:492) > ... 4 more > {noformat} > http://ci.infinispan.org/project.html?projectId=Infinispan&testNameId=-66... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8186) DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges sometimes fails with magic error

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8186?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8186: ----------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5392 > DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges sometimes fails with magic error > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-8186 > URL: https://issues.jboss.org/browse/ISPN-8186 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.0.Final > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 9.1.1.Final > > > Happens sometimes on CI: > DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges > {code} > org.infinispan.client.hotrod.exceptions.InvalidResponseException:: > Invalid magic number. Expected 0xa1 and received 0xdb at > org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:333) at > org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:135) at > org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) at > org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:58) at > org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:34) at > org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) at > org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:268) at > org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:77) at > org.infinispan.client.hotrod.DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges(DistTopologyChangeUnderLoadTest.java:57) at > java.util.concurrent.FutureTask.run(FutureTask.java:266) at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at > java.lang.Thread.run(Thread.java:748) ... Removed 16 stack frames > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8186) DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges sometimes fails with magic error

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8186?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8186: ----------------------------------- Fix Version/s: 9.1.1.Final > DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges sometimes fails with magic error > ---------------------------------------------------------------------------------------------------- > > Key: ISPN-8186 > URL: https://issues.jboss.org/browse/ISPN-8186 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.1.0.Final > Reporter: Tristan Tarrant > Assignee: Galder Zamarreño > Fix For: 9.1.1.Final > > > Happens sometimes on CI: > DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges > {code} > org.infinispan.client.hotrod.exceptions.InvalidResponseException:: > Invalid magic number. Expected 0xa1 and received 0xdb at > org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:333) at > org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:135) at > org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60) at > org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:58) at > org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:34) at > org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56) at > org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:268) at > org.infinispan.client.hotrod.impl.RemoteCacheSupport.put(RemoteCacheSupport.java:77) at > org.infinispan.client.hotrod.DistTopologyChangeUnderLoadTest.testPutsSucceedWhileTopologyChanges(DistTopologyChangeUnderLoadTest.java:57) at > java.util.concurrent.FutureTask.run(FutureTask.java:266) at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at > java.lang.Thread.run(Thread.java:748) ... Removed 16 stack frames > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8222) Jenkins should archive all logs

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8222?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8222: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5391 > Jenkins should archive all logs > ------------------------------- > > Key: ISPN-8222 > URL: https://issues.jboss.org/browse/ISPN-8222 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8222) Jenkins should archive all logs

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8222?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-8222: ----------------------------------------- Assignee: Sebastian Łaskawiec > Jenkins should archive all logs > ------------------------------- > > Key: ISPN-8222 > URL: https://issues.jboss.org/browse/ISPN-8222 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8222) Jenkins should archive all logs

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8222?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-8222: -------------------------------------- Status: Open (was: New) > Jenkins should archive all logs > ------------------------------- > > Key: ISPN-8222 > URL: https://issues.jboss.org/browse/ISPN-8222 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8222) Jenkins should archive all logs

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-8222: ----------------------------------------- Summary: Jenkins should archive all logs Key: ISPN-8222 URL: https://issues.jboss.org/browse/ISPN-8222 Project: Infinispan Issue Type: Enhancement Reporter: Sebastian Łaskawiec -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8221) RemoteCacheStoreIT.testReadOnly random failures

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-8221: ---------------------------------- Summary: RemoteCacheStoreIT.testReadOnly random failures Key: ISPN-8221 URL: https://issues.jboss.org/browse/ISPN-8221 Project: Infinispan Issue Type: Bug Affects Versions: 9.1.0.Final Reporter: Gustavo Fernandes Assignee: Ryan Emerson Fix For: 9.1.1.Final java.lang.AssertionError: expected null, but was:<v1> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotNull(Assert.java:664) at org.junit.Assert.assertNull(Assert.java:646) at org.junit.Assert.assertNull(Assert.java:656) at org.infinispan.server.test.cs.remote.RemoteCacheStoreIT.testReadOnly(RemoteCacheStoreIT.java:85) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8204) Remove should be conditional

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8204?page=com.atlassian.jira.plugin.... ] Pedro Ruivo commented on ISPN-8204: ----------------------------------- There are many changes in semantic. {{IRV}} flag with non-condition removal will create a {{RemoveCommand}} with {{LoadType}} {{DONT_LOAD}}: * the context entry isn't mark as read (skips WriteSkew check) * the value isn't loaded from cache loader if it doesn't exists in {{DataContainer}} * if the entry doesn't exists in context, it won't be loaded from remote node * it doesn't create a {{SuccessfulResponse}} (doesn't send the return value) * in a transaction, it doesn't perform the remote get. My point is that we lose all the {{IRV}} behavior, and that isn't good IMO. If we go we this changes, we can remove the flag (it is only used in {{put(k,v)}} and create a {{set(k,v)}} method. At least, it can remove a couple of if-branches in the code... Also, I would like to know what others think about it. If I'm the only one thinking this way, there is no point in waste time to discuss it :) > Remove should be conditional > ---------------------------- > > Key: ISPN-8204 > URL: https://issues.jboss.org/browse/ISPN-8204 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > > If {{cache.remove(k)}} is called on non-existent key, it should become a no-op, marking the command as unsuccessful, not writing the cache store and not replicating the change to backup owners. That makes the command effectively conditional (as it checks previous value), in the same way as {{cache.replace(k, newValue)}} is. > While I think that this is the correct behaviour, it's a breaking change for transactions. Some transactions may become read-only and there are multiple tests in the testsuite that would be broken by this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2017