You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2011/05/16 14:10:47 UTC
[jira] [Commented] (QPID-3259) Deadlock on Java client side while
closing session when topic operation is unauthorized
[ https://issues.apache.org/jira/browse/QPID-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033985#comment-13033985 ]
Keith Wall commented on QPID-3259:
----------------------------------
Could you update this JIRA with the version number(s) of the broker/client that are affected by the problem? Would you also have a test case that demonstrates the defect?
Kind regards, Keith.
> Deadlock on Java client side while closing session when topic operation is unauthorized
> ---------------------------------------------------------------------------------------
>
> Key: QPID-3259
> URL: https://issues.apache.org/jira/browse/QPID-3259
> Project: Qpid
> Issue Type: Bug
> Environment: Java client runs into a deadlock when it tries to close session when a topic operation (publish/subscribe) is not authorized.
> In this situation AMQConnection (in exceptionReceived) tries to grab failover mutext and runs into a lock.
> The other issue in this case is that AMQException.isHardError always returns true and hence the connection tried to close all sessions inside exceptionReceived method. I think there is something wrong here as an unauthorized operation in one session should not lead to closing all other sessions.
> Reporter: Danushka Menikkumbura
> Priority: Critical
>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org