-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
Undefined
The test fails very often when running the core test suite with trace logging enabled. It assumes the transaction from the fork thread must be added as a lock "owner" immediately after the transaction has been added to the TransactionTable, but under load the main thread's check can happen between the two:
11:33:13,129 TRACE (ForkThread-1,Test:[]) [InfinispanLock] Try acquire. Next in queue=LockPlaceHolder{lockState=WAITING, owner=GlobalTransaction{id=26595, addr=local, remote=false, xid=null, internalId=-1}}. Current=LockPlaceHolder{lockState=ACQUIRED, owner=_tx_} 11:33:13,129 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.locking.RollbackDuringLockAcquisitionTest.testRollbackWhileWaitingForLockDuringLock([true, EmbeddedTransactionManagerLookup]) java.lang.AssertionError: at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?] at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24) ~[testng-6.14.3.jar:?] at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:33) ~[testng-6.14.3.jar:?] at org.infinispan.tx.locking.RollbackDuringLockAcquisitionTest.testRollbackWhileWaitingForLockDuringLock(RollbackDuringLockAcquisitionTest.java:171) ~[test-classes/:?]
- relates to
-
ISPN-13024 Implicit Cache Lock Release Failure
-
- Closed
-