[
https://issues.apache.org/jira/browse/QPID-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036055#comment-13036055
]
Danushka Menikkumbura commented on QPID-3259:
---------------------------------------------
Hi Rajith,
I think we need to fix AMQException.isHardError() so that it correctly figures
out the level of severity rather than returning "true" all the time so that we
know when to close all sessions and eventually the connection.
The normal usecase is that we create one connection and multiple sessions out
of it. Therefore an unauthorized operation in one of them should not cause
others to die.
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]
