+++ This bug was initially created as a clone of Bug #918450 +++ The test randomly fails (but very often) with the error: java.lang.AssertionError at org.infinispan.lucene.DirectoryOnMultipleCachesTest.verifyIntendedLockCachesUsage(DirectoryOnMultipleCachesTest.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) 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:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)
Pedro Ruivo <pedroruivo2> made a comment on jira ISPN-2896 I think that bug is caused by the removeAsync when the value == 0. Simplify code: {code:java} int refCount = refCountObject.intValue(); newValue = refCount - 1; locksCache.replace(readLockKey, refCountObject, newValue); if (newValue == 0) { locksCache.withFlags(Flag.IGNORE_RETURN_VALUES).removeAsync(readLockKey); } {code} So, when the assertion is done, the value can be zero or one. In case of zero, we need to check if the key is really removed.
Seen in 6.1.1.ER3 with Infinispan 5.2.7. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Infinispan/job/eap-6x-infinispan-rhel-matrix/38/jdk=java17_default,label=RHEL6_x86_64/testReport/org.infinispan.lucene/DirectoryOnMultipleCachesTest/verifyIntendedLockCachesUsage/
Sanne Grinovero <sanne+jbossorg> updated the status of jira ISPN-2896 to Closed
These issues are specific to the Infinispan testsuite, and either reside in modules that are not used in EAP, or pertain to use cases that are not supported in EAP. Setting resolution to WONTFIX.