Rashmi

Hello Ban, Thanks a lot for your help so far !! Can you please help to clarify one more doubt.. We have these proeprties set: jgroups_cluster.property_string=TCP(bind_addr=172.20.242.100;bind_port=8241):TCPPING(initial_hosts=172.20.242.100[8241],172.20.242.100[8256],172.20.242.105[8241],172.20.242.105[8256],172.20.242.106[8241],172.20.242.106[8256];port_range=0;timeout=5000;num_initial_members=2):MERGE2(min_interval=3000;max_interval=5000):FD_ALL(interval=5000;timeout=20000):FD(timeout=5000;max_tries=48;level=ERROR):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK2(use_mcast_xmit=false;retransmit_timeout=100,200,300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST3:pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(print_local_addr=true;join_timeout=5000)...

That is not an option, since it is working for all customers. one specific scenario is not working. you see anything specific to IPV6 or something here ?

We are using Jgroup 3.4.1 . Customer is using 6 nodes in the network and after restart, imeediately within 40s , receiveing the message saying haven't received a heartbeat from 2432c2fa-acda-c0c0-3f88-469b7781f968 for 41088 ms, adding it to suspect list .. CLuster communcation is broken with this error. Customer is using WIndiws 2012 R2 with IPV6 underlying network and want cluster communication in TCP. I saw below thread, where suggesting to use FD_ALL and Change rejection policy from "run" to "discard",...