December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2315) PessimisticDistTxTest.testTxInProgress2 and testTxInProgress1 fail randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2315?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2315: -------------------------------- Fix Version/s: (was: 5.2.0.CR1) > PessimisticDistTxTest.testTxInProgress2 and testTxInProgress1 fail randomly > --------------------------------------------------------------------------- > > Key: ISPN-2315 > URL: https://issues.jboss.org/browse/ISPN-2315 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.2.0.Final > > Attachments: testTxInProgress1-1.log > > > {code}Failed tests: testTxInProgress2(org.infinispan.tx.locking.PessimisticDistTxTest): expected:<false> but was:<true>{code} > Logs: https://dl.dropbox.com/u/6148072/testTxInProgress2-0.tgz -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2653) LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2653?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2653: -------------------------------- Fix Version/s: (was: 5.2.0.CR1) > LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly > ---------------------------------------------------------------------- > > Key: ISPN-2653 > URL: https://issues.jboss.org/browse/ISPN-2653 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.2.0.Final > > > LocalKeyAffinityServiceTest.testFilteredRemoveServers failing randomly: > {code}testFilteredRemoveServers(org.infinispan.affinity.LocalKeyAffinityServiceTest) Time elapsed: 0.054 sec <<< FAILURE! > java.lang.AssertionError: expected [true] but found [false] > at org.testng.Assert.fail(Assert.java:89) > at org.testng.Assert.failNotEquals(Assert.java:489) > at org.testng.Assert.assertTrue(Assert.java:37) > at org.testng.Assert.assertTrue(Assert.java:47) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:76) > at org.infinispan.test.AbstractInfinispanTest.eventually(AbstractInfinispanTest.java:59) > at org.infinispan.affinity.BaseKeyAffinityServiceTest.assertEventualFullCapacity(BaseKeyAffinityServiceTest.java:98) > at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.assertUnaffected(BaseFilterKeyAffinityServiceTest.java:108) > at org.infinispan.affinity.BaseFilterKeyAffinityServiceTest.testRemoveServers(BaseFilterKeyAffinityServiceTest.java:82) > at org.infinispan.affinity.LocalKeyAffinityServiceTest.testFilteredRemoveServers(LocalKeyAffinityServiceTest.java:66) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > 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:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680){code} > TRACE log coming up... -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2482) Simplify XSite configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2482?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2482: -------------------------------- Fix Version/s: (was: 5.2.0.CR1) > Simplify XSite configuration > ---------------------------- > > Key: ISPN-2482 > URL: https://issues.jboss.org/browse/ISPN-2482 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.2.0.Final > > > The relay.xml configuration file which is referred from the local cluster's jgroups.xml can be code-injected in JGroups directly. Nice to have a simplified configuration file. > Sample code for the code-injection is Relay2Test -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2542) AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2542?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2542: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR1) > AsyncStoreTest.testRestrictionOnAddingToAsyncQueue fails randomly > ----------------------------------------------------------------- > > Key: ISPN-2542 > URL: https://issues.jboss.org/browse/ISPN-2542 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 5.2.0.Final > > Attachments: testRestrictionOnAddingToAsyncQueue-2.log.zip > > > {code}testRestrictionOnAddingToAsyncQueue(org.infinispan.loaders.decorators.AsyncStoreTest): > Method org.testng.internal.TestNGMethod.testRestrictionOnAddingToAsyncQueue() didn't finish within the time-out 10000{code} -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2300) Versioned Transactional Cache issues

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2300?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2300: -------------------------------- Priority: Critical (was: Major) > Versioned Transactional Cache issues > ------------------------------------ > > Key: ISPN-2300 > URL: https://issues.jboss.org/browse/ISPN-2300 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 5.2.0.Alpha3 > Reporter: Pedro Ruivo > Assignee: Galder Zamarreño > Priority: Critical > Labels: Commands, Conditional, Transactions, Version > Fix For: 5.2.0.CR1, 5.2.0.Final > > > Description from http://lists.jboss.org/pipermail/infinispan-dev/2012-September/011205.html > 1) testPutIfAbsent, testRemoveIfPresent, testReplaceWithOldVal (methods > the test cases) > In this tests, it was updating the cache entry with a null version. This > originates later a IllegalStateException when it tries to perform the > write skew check and the version is null. > I have fixed this problem in this way: if the command fails (PutCommand, > RemoveCommand, ReplaceCommand), I unset the flag CHANGED in the > MvccEntry to avoid to update the entry in the DataContainer. > 2) testClear in distributed mode > I have no clear idea how to solve this problem but it looks like the > PrepareCommand (with the ClearCommand) is not sent to all the nodes in > the cluster. Then, when I do a get, a remote get is performed and the > key is still there. I think that it is not the desired behavior. > 3) testRemoveUnexistingEntry > In this test, it tries to remove a key that does not exists but it does > not success due to a NullPointerException. I have looked deeper and I > check that the transaction's lookup entries map has an entry with [key > => null] and when it tries to perform the write skew check in that key, > a NullPointerException is thrown in here [2] (line 80, WriteSkewHelper) > [1] https://github.com/pruivo/infinispan/tree/t_replace_fix > [2] https://github.com/pruivo/infinispan/blob/t_replace_fix/core/src/main/jav... -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2647) ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2647?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2647: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR1) > ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-2647 > URL: https://issues.jboss.org/browse/ISPN-2647 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseDistStateTransferConsistencyTest.testReplace() and BaseReplStateTransferConsistencyTest.testReplace(). -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2581) StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2581?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2581: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR1) > StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns too soon > --------------------------------------------------------------------------------- > > Key: ISPN-2581 > URL: https://issues.jboss.org/browse/ISPN-2581 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Dan Berindei > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.2.0.Final > > > StateTransferManagerImpl.waitForInitialStateTransferToComplete() returns as soon as a joining node confirmed to the coordinator that it received all the data it needed (see STMI.notifyEndOfTopologyUpdate()). > It should return only after the coordinator has confirmed the end of the rebalance with a new topology update (see STMI.doTopologyUpdate()). > This should make it more likely for the tests suite clusters to be in a stable state by the time the test starts, and should help with the random state transfer-related failures in non-state transfer tests. > Instead we should make sure that we do have tests that check forwarding behaviour explicitly. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2511) RemoteExceptionHandlingWithStateTransferTest.testThrowExceptionFromRemoteInterceptor fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2511?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2511: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR1) > RemoteExceptionHandlingWithStateTransferTest.testThrowExceptionFromRemoteInterceptor fails randomly > --------------------------------------------------------------------------------------------------- > > Key: ISPN-2511 > URL: https://issues.jboss.org/browse/ISPN-2511 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Reporter: Anna Manukyan > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 5.2.0.Final > > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > The test works properly, when run separately. More logs will be provided later. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2510) PrepareCommands should fail on nodes where the cache is not running

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2510?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2510: -------------------------------- Fix Version/s: (was: 5.2.0.CR1) > PrepareCommands should fail on nodes where the cache is not running > ------------------------------------------------------------------- > > Key: ISPN-2510 > URL: https://issues.jboss.org/browse/ISPN-2510 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache, RPC > Affects Versions: 5.2.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.2.0.Final > > > When the user stops a cache without stopping the cache manager on that node, subsequent PrepareCommands sent to that node will return a {{SuccessfulResponse}}. > If that node used to the primary owner of the command's modified key, the originator will proceed with the transaction as if it had acquired a lock on that key. It is thus possible for multiple transactions to think they have acquired the key lock at the same time. > On the other hand, in replicated caches is is quite possible that a cache is not running on all the cluster node and yet PrepareCommands are broadcasted to everyone in parallel. So the solution should not involve sending exceptions (which have huge stack traces), and the originator should be able to ignore failures responses from nodes that were not targeted in the first place. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2537) LockCleanupStateTransferTest fails randomly

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2537?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2537: -------------------------------- Fix Version/s: 5.2.0.Final (was: 5.2.0.CR1) > LockCleanupStateTransferTest fails randomly > ------------------------------------------- > > Key: ISPN-2537 > URL: https://issues.jboss.org/browse/ISPN-2537 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 5.2.0.Beta4 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 5.2.0.Final > > > LockCleanupStateTransferTest assumes that once the tx is done on one remote node it's done on all of them (and on the originator as well). > It sometimes fails with this stack trace: > {noformat} > java.lang.AssertionError: For cache 0 expected:<0> but was:<1> > at org.junit.Assert.fail(Assert.java:93) > at org.junit.Assert.failNotEquals(Assert.java:647) > at org.junit.Assert.assertEquals(Assert.java:128) > at org.junit.Assert.assertEquals(Assert.java:472) > at org.infinispan.tx.LockCleanupStateTransferTest.testLockReleasedCorrectly(LockCleanupStateTransferTest.java:164) > at org.infinispan.tx.LockCleanupStateTransferTest.testBelatedCommit(LockCleanupStateTransferTest.java:76) > {noformat} -- 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

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012