In an Access Gateway cluster when multiple nodes are down, failover does not occur and the user experiences looping due to jgroups issues.
Workaround: Modify the /opt/novell/nesp/lib/webapp/WEB-INF/web.xml file on the Access Gateway server as follows to increase the jgroup timeouts:
<param-name>JGroupsConfiguration</param-name> <param-value> TCP(start_port=[nidp:ClusterPort];end_port=[nidp:ClusterPort][nidp:IfExternalAddress];external_addr=[nidp:ExternalAddress][nidp:EndIf]):TCPPING(initial_hosts=[nidp:ClusterMembers];port_range=1;timeout=20000;num_initial_members=2;up_thread=true;down_thread=true):MERGE2(min_interval=10000;max_interval=30000):FD_SOCK([nidp:IfExternalAddress]bind_addr=[nidp:ExternalAddress][nidp:EndIf]):FD(shun=true;timeout=20000;max_tries=5;up_thread=true;down_thread=true):VERIFY_SUSPECT(timeout=20000;down_thread=false;up_thread=false):pbcast.NAKACK(down_thread=true;up_thread=true;gc_lag=100;retransmit_timeout=3000):pbcast.STABLE(desired_avg_gossip=20000;down_thread=false;up_thread=false):pbcast.STATE_TRANSFER():pbcast.GMS(merge_timeout=90000;join_timeout=60000;join_retry_timeout=60000;shun=true;print_local_addr=[nidp:DebugOn];down_thread=true;up_thread=true) </param-value>
NOTE:By default, web.xml does not contain the JGroupsConfiguration parameter. You need to add it when required.
For more information about the timeout options, see the following links: