[jboss-jira] [JBoss JIRA] (JGRP-1761) LockServiceTest: deadlock

Bela Ban (JIRA) issues at jboss.org
Fri Dec 20 09:45:35 EST 2013


Bela Ban created JGRP-1761:
------------------------------

             Summary: LockServiceTest: deadlock
                 Key: JGRP-1761
                 URL: https://issues.jboss.org/browse/JGRP-1761
             Project: JGroups
          Issue Type: Bug
            Reporter: Bela Ban
            Assignee: Bela Ban
             Fix For: 3.5


{noformat}

Found one Java-level deadlock:
   =============================
   "Thread-157":
     waiting to lock monitor 0x00007fc2d0002a98 (object 0x00000000ceed9348, a org.jgroups.protocols.Locking$ClientLockTable),
     which is held by "pool-2-thread-10"
   "pool-2-thread-10":
     waiting to lock monitor 0x00007fc2d0002b48 (object 0x00000000cf48bc30, a org.jgroups.protocols.Locking$ClientLock),
     which is held by "Thread-157"
   
   Java stack information for the threads listed above:
   ===================================================
   "Thread-157":
       at org.jgroups.protocols.Locking$ClientLockTable.removeClientLock(Locking.java:1030)
       - waiting to lock <0x00000000ceed9348> (a org.jgroups.protocols.Locking$ClientLockTable)
       at org.jgroups.protocols.Locking$ClientLock._unlock(Locking.java:947)
       - locked <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock)
       at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:878)
       - locked <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock)
       at org.jgroups.protocols.Locking.down(Locking.java:160)
       at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1034)
       at org.jgroups.JChannel.down(JChannel.java:765)
       at org.jgroups.blocks.locking.LockService$LockImpl.unlock(LockService.java:161)
       at org.jgroups.blocks.LockServiceTest.unlock(LockServiceTest.java:486)
       at org.jgroups.blocks.LockServiceTest$AbstractAwaiter.run(LockServiceTest.java:366)
       at java.lang.Thread.run(Thread.java:724)
   "pool-2-thread-10":
       at org.jgroups.protocols.Locking$ClientLock.unlock(Locking.java:878)
       - waiting to lock <0x00000000cf48bc30> (a org.jgroups.protocols.Locking$ClientLock)
       at org.jgroups.protocols.Locking$ClientLockTable.unlockAll(Locking.java:1046)
       - locked <0x00000000ceed9348> (a org.jgroups.protocols.Locking$ClientLockTable)
       at org.jgroups.protocols.Locking.unlockAll(Locking.java:282)
       at org.jgroups.protocols.Locking.down(Locking.java:164)
       at org.jgroups.stack.ProtocolStack.down(ProtocolStack.java:1034)
       at org.jgroups.JChannel.down(JChannel.java:765)
       at org.jgroups.blocks.locking.LockService.unlockAll(LockService.java:65)
       at org.jgroups.blocks.LockServiceTest.unlockAll(LockServiceTest.java:57)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
       at java.lang.reflect.Method.invoke(Method.java:606)
       at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
       at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
       at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
       at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
       at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
       at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
       at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
       at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
       at java.lang.Thread.run(Thread.java:724)
   
   Found 1 deadlock.
{noformat}

--
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


More information about the jboss-jira mailing list