Bela Ban created JGRP-1610: ------------------------------ Summary: LockingService and rpc on the same cluster, tryLock() hangs Key: JGRP-1610 URL: https://issues.jboss.org/browse/JGRP-1610 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.3 Attachments: RpcLockingTest.java Hi, Yes, the sequence diagram only depicted the second part of my description. Anyway, I've attached a test file that reproduce the problem. It contains two test cases, one where the coordinator of the lock is the one who sends the message first, and a second case where the non-coordinator sends the message first. In the first case the receiver, non-coordinator, will hang in tryLock. In the second case though, everything works fine. Regards, Daniel Olausson On 25 March 2013 16:15, Bela Ban <belaban(a)yahoo.com&gt; wrote: Hi Daniel, the sequence diagram differs from your description, can you submit a test case (e.g. copy MessageDispatcherRSVPTest and modify it), so I can take a look ? I assume your RPCs are blocking (sync) and non-OOB ? Could be a recursive invocation, where FIFO order (default) leads to a distributed deadlock. A test case would clarify what you want to do, and if I can reproduce the problem, I can fix it. On 3/25/13 1:54 PM, Daniel Olausson wrote: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira