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/23 17:31:35 UTC
[jira] [Created] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Alan Conway created QPID-4163:
---------------------------------
Summary: 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
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
[jira] [Resolved] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420977#comment-13420977 ]
Alan Conway commented on QPID-4163:
-----------------------------------
Comitted to trunk r1364805
> 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
[jira] [Commented] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Posted by "Justin Ross (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420769#comment-13420769 ]
Justin Ross commented on QPID-4163:
-----------------------------------
Reviewed by Gordon and Andrew. Approved for 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
[jira] [Comment Edited] (QPID-4163) Deadlock between LinkRegistry
and TimerTask locks
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420742#comment-13420742 ]
Alan Conway edited comment on QPID-4163 at 7/23/12 4:16 PM:
------------------------------------------------------------
Code review of fix: https://reviews.apache.org/r/6092
Request merge to 0.18
was (Author: aconway):
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
[jira] [Updated] (QPID-4163) Deadlock between LinkRegistry and
TimerTask locks
Posted by "Alan Conway (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated QPID-4163:
------------------------------
Attachment: ha-timer-hang.pstack
Stack trace of hung broker
> 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