]
Mircea Markus commented on ISPN-2305:
-------------------------------------
Extracted the 2nd issue into a different ISPN-2314
ConcurrentCacheManagerTest hangs up
-------------------------------------
Key: ISPN-2305
URL:
https://issues.jboss.org/browse/ISPN-2305
Project: Infinispan
Issue Type: Bug
Components: Core API
Reporter: Galder ZamarreƱo
Assignee: Mircea Markus
Priority: Blocker
Labels: testsuite_stability
Fix For: 5.2.0.Alpha4
Attachments: concurrent-cachemanager-test-threaddump.log
Several issues that appear to be rooted in ISPN-2256:
1. ConcurrentCacheManagerTest hangs
{code}"testng-ConcurrentCacheManagerTest" prio=5 tid=7fb8ca077800
nid=0x115b97000 waiting on condition [115b95000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <7d5d373b8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
at java.util.concurrent.CyclicBarrier.dowait(CyclicBarrier.java:199)
at java.util.concurrent.CyclicBarrier.await(CyclicBarrier.java:327)
at
org.infinispan.manager.ConcurrentCacheManagerTest.testConcurrentGetCacheCalls(ConcurrentCacheManagerTest.java:94){code}
2. Query tests fail with messages like:
{code} testLocalQueryCacheRestart(org.infinispan.query.blackbox.QueryCacheRestartTest):
It was expected to find the Query interceptor registered in the InterceptorChain but it
wasn't found{code}
This was working fine in
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/814/co..., so
since the issue appears to be related to cache startup, it's almost for sure related
to ISPN-2256 (appeared in
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/815/co...).
Btw, as part of fixing up ISPN-2290 to avoid duplicate domains, I'm making the tests
that caused the testsuite to halt more resilient.
--
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: