I am posting the solution that I have put in for the problem posted here. I
changed the cluster config to use instead of <FD_SOCK> and am no longer
experiencing the timeout issue.
The cluster documentation mentions that when FD_SOCK is used, a member is
declared dead only when socket is closed. This was the reason why when a node
was "unplugged" from the network without graceful shutdown, we were
experiencing problems on the other nodes. By using , heart beat messages will
be used for failure detection and hence node exits can be detected even without
graceful shutdown.
My config entry now uses :
<FD shun="true" up_thread="true" down_thread="true"/>
Bela, I am still interested in finding out what I am missing in terms of the
clusters not being separate. Really appretiate any pointers you may have on
that regard.
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914614#3914614
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914614
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
