You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2015/03/09 18:56:38 UTC
[jira] [Comment Edited] (QPID-6437) [Java broker] [AMQP 1.0]
deadlock if flow arrives as consumer is being notified queue is empty
[ https://issues.apache.org/jira/browse/QPID-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353281#comment-14353281 ]
Justin Ross edited comment on QPID-6437 at 3/9/15 5:55 PM:
-----------------------------------------------------------
Tested by Robbie. Approved for 0.32.
http://qpid.2158936.n2.nabble.com/0-32-release-update-Beta-is-available-td7620610.html
was (Author: justi9):
Tested by Robbie. Approved for 0.32.
> [Java broker] [AMQP 1.0] deadlock if flow arrives as consumer is being notified queue is empty
> ----------------------------------------------------------------------------------------------
>
> Key: QPID-6437
> URL: https://issues.apache.org/jira/browse/QPID-6437
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.32
> Reporter: Robbie Gemmell
> Attachments: jstack.txt
>
>
> I observed a deadlock when running some tests against the Java broker using the new JMS client, apparently occurring when a flow arrived at the broker at the same time a QueueRunner was notifying a consumer that the queue was empty.
> This further meant that the broker could not be shutdown with a CTRL-C since the shutdown hook waited for one of the locks involved.
> Stack output to be attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org