[jboss-jira] [JBoss JIRA] Created: (JGRP-392) disconnect() hangs forever on second client of group

[?yvind Eikeland (JIRA)]

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


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