You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2008/05/02 17:22:55 UTC
[jira] Commented: (QPID-1000) Deadlock in unit.basic.SelectorTest
[ https://issues.apache.org/jira/browse/QPID-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593796#action_12593796 ]
Martin Ritchie commented on QPID-1000:
--------------------------------------
The synchronized nature of onMessage and test() is causing the issue. the synchronized needs dropping to be just around the wait or swap for a countdown latch.
> Deadlock in unit.basic.SelectorTest
> -----------------------------------
>
> Key: QPID-1000
> URL: https://issues.apache.org/jira/browse/QPID-1000
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Reporter: Martin Ritchie
> Attachments: QPID-1000-SelectorTest-DeadLock.txt
>
>
> Summary:
> running ant then ant test resulted in this deadlock, Full Thread dump attached as file.
> Found one Java-level deadlock:
> =============================
> "Dispatcher-Channel-1":
> waiting to lock monitor 0x02a602dc (object 0x23a37cc8, a org.apache.qpid.test.unit.basic.SelectorTest),
> which is held by "main"
> "main":
> waiting to lock monitor 0x02a60274 (object 0x22bd27e8, a java.lang.Object),
> which is held by "Dispatcher-Channel-1"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.