[
https://issues.apache.org/jira/browse/QPID-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036629#comment-13036629
]
Danushka Menikkumbura commented on QPID-3259:
---------------------------------------------
Hi Rajith,
This is actually a deadlock, session lock times out after some time though.
Sadly Qpid is full of such fundamental issue. I just unveiled a similar issue
when I tried to close session after sending large number of messages in a row.
I think we need to get into hackathon mode and fix them. Qpid is a great
product but if you try to use it in real production environment you will end up
with all sorts of weird behaviours.
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
> Assignee: Rajith Attapattu
> 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]
