[
http://jira.jboss.com/jira/browse/JGRP-532?page=comments#action_12365524 ]
Bela Ban commented on JGRP-532:
-------------------------------
We need to revert the rejection level to "run", otherwise performance is worse.
The stack trace below shows that STABLE needs to release the lock on NakReceiverWindow
before passing down the message, which would prevent the deadlock. This is related to
535.
"Incoming Thread,perf,192.168.0.5:7801" daemon prio=10 tid=0x00002aaacba7ac00
nid=0x24b6 waiting on condition [0x0000000040aa9000..0x0000000040aa9d10]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00002aaab4046dd8> (a
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1889)
at java.util.concurrent.LinkedBlockingQueue.put(LinkedBlockingQueue.java:254)
at
org.jgroups.blocks.BasicConnectionTable$Connection.send(BasicConnectionTable.java:433)
at org.jgroups.blocks.BasicConnectionTable.send(BasicConnectionTable.java:243)
at org.jgroups.protocols.TCP.send(TCP.java:54)
at org.jgroups.protocols.BasicTCP.sendToSingleMember(BasicTCP.java:194)
at org.jgroups.protocols.BasicTCP.sendToAllMembers(BasicTCP.java:179)
at org.jgroups.protocols.TP.doSend(TP.java:1187)
at org.jgroups.protocols.TP.send(TP.java:1177)
at org.jgroups.protocols.TP.down(TP.java:944)
at org.jgroups.protocols.Discovery.down(Discovery.java:321)
at org.jgroups.protocols.MERGE2.down(MERGE2.java:184)
at org.jgroups.protocols.FD_SOCK.down(FD_SOCK.java:403)
at org.jgroups.protocols.FD.down(FD.java:363)
at org.jgroups.stack.Protocol.down(Protocol.java:252)
at org.jgroups.protocols.BARRIER.down(BARRIER.java:97)
at org.jgroups.protocols.pbcast.NAKACK.send(NAKACK.java:648)
at org.jgroups.protocols.pbcast.NAKACK.down(NAKACK.java:438)
at org.jgroups.protocols.UNICAST.down(UNICAST.java:430)
at org.jgroups.protocols.pbcast.STABLE.sendStableMessage(STABLE.java:640)
at org.jgroups.protocols.pbcast.STABLE.handleRegularMessage(STABLE.java:286)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:233)
at org.jgroups.protocols.UNICAST.up(UNICAST.java:263)
at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:720)
- locked <0x00002aaab404afc0> (a org.jgroups.stack.NakReceiverWindow)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:546)
at org.jgroups.protocols.BARRIER.up(BARRIER.java:122)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:154)
at org.jgroups.protocols.FD.up(FD.java:328)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:298)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:145)
at org.jgroups.protocols.Discovery.up(Discovery.java:220)
at org.jgroups.protocols.MPING.up(MPING.java:151)
at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1542)
at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1491)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
TCP: hangs without FC
---------------------
Key: JGRP-532
URL:
http://jira.jboss.com/jira/browse/JGRP-532
Project: JGroups
Issue Type: Bug
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.5
Attachments: config.txt, tcp.xml, tmp.txt
Usually, FC is enabled, but when FC is not present, perf.Test with 2 senders and the
attached tcp.xml/config.txt hangs. Stack trace attached too.
--
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