[
http://jira.jboss.com/jira/browse/JGRP-392?page=comments#action_12349053 ]
r p commented on JGRP-392:
--------------------------
I've see this behaviour as well. channel.disconnect() hangs. This appeared after I
switched from a TCP protocol to a TCP_NIO protocol.
I've tried with both <FD /> and <FD /> + <FD_SOCK /> stack.
Here is the config:
<TCP_NIO
recv_buf_size="20000000"
send_buf_size="640000"
loopback="false"
discard_incompatible_packets="true"
max_bundle_size="64000"
max_bundle_timeout="30"
use_incoming_packet_handler="true"
use_outgoing_packet_handler="true"
down_thread="false"
up_thread="false"
enable_bundling="true"
start_port="7800"
use_send_queues="false"
sock_conn_timeout="300"
skip_suspected_members="false"
reader_threads="8"
writer_threads="8"
processor_threads="8"
processor_minThreads="8"
processor_maxThreads="8"
processor_queueSize="100"
processor_keepAliveTime="-1"/>
<MPING
timeout="2000"
num_initial_members="2"
mcast_addr="229.6.7.8"
down_thread="false"
up_thread="false"/>
<pbcast.NAKACK
max_xmit_size="60000"
use_mcast_xmit="false"
gc_lag="10"
retransmit_timeout="100,200,300,600,1200,2400,4800"
down_thread="false"
up_thread="false"
discard_delivered_msgs="true" />
<pbcast.STABLE
stability_delay="1000"
desired_avg_gossip="50000"
down_thread="false"
up_thread="false"
max_bytes="400000"/>
<pbcast.GMS
print_local_addr="true"
join_timeout="3000"
down_thread="false"
up_thread="false"
join_retry_timeout="2000"
shun="true"/>
<FD_SOCK down_thread="false" up_thread="false"/>
<FD
timeout="10000"
max_tries="5"
down_thread="false"
up_thread="false"
shun="true"/>
<MERGE2
min_interval="500"
max_interval="1000"
down_thread="false"
up_thread="false" />
<VERIFY_SUSPECT
timeout="1500"
down_thread="false"
up_thread="false"/>
<pbcast.STREAMING_STATE_TRANSFER
down_thread="false"
up_thread="false"
use_flush="true"
use_reading_thread="true"/>
<pbcast.FLUSH
down_thread="false"
up_thread="false"/>
disconnect() hangs forever on second client of group
----------------------------------------------------
Key: JGRP-392
URL:
http://jira.jboss.com/jira/browse/JGRP-392
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4
Environment: Windows XP.
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
"UDP(mcast_addr=239.10.10.10;mcast_port=17000" +
";ip_ttl=8;" +
"mcast_send_buf_size=150000;mcast_recv_buf_size=80000):" +
"PING(timeout=2000;num_initial_members=3):" +
"MERGE2(min_interval=5000;max_interval=10000):" +
"FD_SOCK:" +
"VERIFY_SUSPECT(timeout=1500):" +
"pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800):" +
"UNICAST(timeout=5000):" +
"pbcast.STABLE(desired_avg_gossip=20000):" +
"FRAG(frag_size=4096;down_thread=false;up_thread=false):" +
"pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;" +
"shun=false;print_local_addr=true):" +
"pbcast.STATE_TRANSFER";
Reporter: ?yvind Eikeland
Assigned To: Bela Ban
Fix For: 2.5
Quite often, but not every time, when member 2 (not the coordinator) is disconnecting
from the group, it will wait forever. This may be some configuration or network issue, but
it would be very useful if a timeout could be specified in the JChannel.disconnect()
method to get around this problem. Members are running in separate JVMs.
when a member/client is leaving a channel, we're calling these methods:
- channel.disconnect();
- channel.close();
This method is called from disconnect() today:
disconnect_promise.getResult(); // wait for DISCONNECT_OK
Instead, disconnect_promise.getResult(timeout); should be called. It does not seem to be
possible to configure this timeout in the protocol stack
--
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