[
http://jira.jboss.com/jira/browse/JBAS-3004?page=all ]
Brian Stansberry closed JBAS-3004.
----------------------------------
Resolution: Done
Done for cluster-service.xml and tcX-cluster.sar; separate issue for the EJB3 caches.
For FD I used a 20 sec timeout with 5 tries; total is 1 min 40 secs which I think is long
enough to prevent false suspicions while not so long that FD_SOCK failures are ignored for
long periods.
Use a combination of FD and FD_SOCK in the default JGroups protocol
stack.
--------------------------------------------------------------------------
Key: JBAS-3004
URL:
http://jira.jboss.com/jira/browse/JBAS-3004
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1
FD_SOCK to promptly detect most issues. FD with a long (say 2 min) timeout as a backup
to detect things like machine/switch crashes where FD_SOCK isn't aware of the TCP
connection failure. Long timeout avoids false suspicions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira