qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Conway (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-4163) Deadlock between LinkRegistry and TimerTask locks
Date Mon, 23 Jul 2012 16:13:34 GMT

    [ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420742#comment-13420742

Alan Conway commented on QPID-4163:

Code review of fix:  https://reviews.apache.org/r/6093/
Request merge to 0.18 
> Deadlock between LinkRegistry and TimerTask locks
> -------------------------------------------------
>                 Key: QPID-4163
>                 URL: https://issues.apache.org/jira/browse/QPID-4163
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.17
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.18
>         Attachments: ha-timer-hang.pstack
> Very occasionally (about 2% of runs), when running ha_tests.py in a long loop one of
the brokers deadlocks with the attached stack trace. The problem is a call to TimerTask::cancel
with the LinkRegsitry lock held, while another thread is in TimerTask::fire and waiting for
the LinkRegistry lock.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message