[
https://jira.jboss.org/jira/browse/JBMESSAGING-1485?page=com.atlassian.ji...
]
Howard Gao commented on JBMESSAGING-1485:
-----------------------------------------
This relates to the fix for
https://jira.jboss.org/jira/browse/JBMESSAGING-1482 (Client
remoting configuration not properly passed to jboss remoting).
before the client configuration (in JBM bisocket, validatorPingPeriod is 10 sec and
validatorPingTimeout is 5 sec) is just ignored and default (2 sec and 1 sec respectively)
is used. Some clustering tests wait for 5 sec to expect the failure detection to happen,
which is fine in the past. But after the 1482 fix, this time is not sufficient. The
sleeping time for a failure detection should be no less than
validatorPingPeriod + validatorPingTimeout
So for 5 sec sleeping time, the validatorPingPeriod and validatorPingTimeout should be 3
sec and 2 sec at least, consider the timing is not so accurate, we can make them 2 sec and
2 sec respectively.
Fix ClusterViewUpdateTest
-------------------------
Key: JBMESSAGING-1485
URL:
https://jira.jboss.org/jira/browse/JBMESSAGING-1485
Project: JBoss Messaging
Issue Type: Bug
Reporter: Clebert Suconic
Assignee: Howard Gao
Priority: Blocker
Fix For: 1.4.0.SP3.CP05
There is a test broken on ClusterViewUpdateTest. The entire clustered testsuite will fail
because of this test failing (something left unnatended on tearDown or finalize blocks)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira