[
https://issues.jboss.org/browse/ISPN-5495?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-5495:
------------------------------------
I fixed my comment... On NodeA (the coordinator), the first command received is still
{{CacheTopologyControlCommand(POLICY_GET_STATUS)}}. On NodeB, the first command is now
{{CacheTopologyControlCommand(GET_STATUS)}}, because NodeA is now trying to recover the
cluster status on startup. NodeA still sends the
{{CacheTopologyControlCommand(POLICY_GET_STATUS)}} command to NodeB, but only after NodeB
receives the response to its {{POLICY_GET_STATUS}} command (because of the locking on
{{GlobalComponentRegistry}}).
ConcurrentStartTest.testConcurrentStart random failures
-------------------------------------------------------
Key: ISPN-5495
URL:
https://issues.jboss.org/browse/ISPN-5495
Project: Infinispan
Issue Type: Bug
Components: Core, Test Suite - Core
Affects Versions: 7.2.1.Final
Reporter: Dan Berindei
Priority: Blocker
Labels: testsuite_stability
Fix For: 8.2.0.CR1
{noformat}
org.testng.internal.thread.ThreadTimeoutException: Method
org.testng.internal.TestNGMethod.testConcurrentStart() didn't finish within the
time-out 60000
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:338)
at org.infinispan.test.TestingUtil.waitForRehashToComplete(TestingUtil.java:253)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)