You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2012/07/24 15:36:34 UTC
[jira] [Resolved] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway resolved QPID-4163.
-------------------------------
Resolution: Fixed
Comitted to 0.18 branch r1365045
> 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