[
https://issues.apache.org/jira/browse/QPID-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036051#comment-13036051
]
Danushka Menikkumbura commented on QPID-3259:
---------------------------------------------
Hi Keith,
Please find the attached thread dump (QPID-3259-ThreadDump) and sample client
(QPID-3259-SampleClient). You can reproduce this issue easily with the latest
trunk (rev. 1124557) using the sample client programme. You need to set
permission so that the user guest can not publish to topic MyTopic. I think you
can simply do this (a shortcut ;-)) by changing the execution path in
ServerSessionDelegate.java(307) to trigger an exception even when the operation
is authorized.
Thanks,
Danushka
> 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
> Attachments: QPID-3259-SampleClient, QPID-3259-ThreadDump
>
>
--
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:[email protected]
