[jgroups-dev] JVM hung on JChannel.connect

Hi,

I have a scenario where there are 2 nodes in a JGroups cluster across 2
machines(Node1 as primary/coordinator and Node2 as secondary). While
restarting Node2 it got stuck and in the threaddump the following was
noticed...

"ServerTask-1" prio=10 tid=0x00007fddc40d8800 nid=0x77ce waiting on
condition [0x00007fde0a2e9000]
   java.lang.Thread.State: TIMED_WAITING (parking)
	at sun.misc.Unsafe.park(Native Method)
	- parking to wait for  <0x00000000ac19b010> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226)
	at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2176)
	at org.jgroups.util.Promise.doWait(Promise.java:117)
	at org.jgroups.util.Promise._getResultWithTimeout(Promise.java:73)
	at org.jgroups.util.Promise.getResultWithTimeout(Promise.java:42)
	at org.jgroups.util.Promise.getResult(Promise.java:104)
	at
org.jgroups.protocols.pbcast.ClientGmsImpl.joinInternal(ClientGmsImpl.java:142)
	at org.jgroups.protocols.pbcast.ClientGmsImpl.join(ClientGmsImpl.java:38)
	at org.jgroups.protocols.pbcast.GMS.down(GMS.java:924)
	at org.jgroups.protocols.FC.down(FC.java:430)
	at org.jgroups.protocols.FRAG2.down(FRAG2.java:154)
	at
org.jgroups.protocols.pbcast.STREAMING_STATE_TRANSFER.down(STREAMING_STATE_TRANSFER.java:331)
	at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:836)
	at org.jgroups.JChannel.downcall(JChannel.java:1652)
	at org.jgroups.JChannel.connect(JChannel.java:417)
	- locked <0x00000000ac19b330> (a org.jgroups.JChannel)
	at *org.jgroups.JChannel.connect(JChannel.java:380)*

But while stopping Node2 the Node1 had received a message that member Node2
left the cluster. But while starting Node2 the above scenario was
encountered. When the entire cluster was restarted ie Node1 followed by
Node2 everything started working. Could it be possible that if
Node1(coordinator) jvm was not responding(due to some other issues) to Node2
this could have happened. Also this problem is not reproducable. *tcp.xml
used is attached for reference. JGroups version is 2.8.0.GA.*

The following system args are used-
-Djava.net.preferIPv4Stack=true
-Djgroups.start_port=5555
-Djgroups.bind_addr=hostname<01>
-Djgroups.tcpping.initial_hosts=hostname<01>[5555],hostname<02>[6666]
 
Kindly provide your valuable suggestions on this.

Regards,
Balu Nair tcp.xml <http://jgroups.1086181.n5.nabble.com/file/n10482/tcp.xml>  



--
View this message in context: http://jgroups.1086181.n5.nabble.com/JVM-hung-on-JChannel-connect-tp10482.html
Sent from the JGroups - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Javagroups-development mailing list