You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2017/04/27 21:36:04 UTC
[jira] [Updated] (ARTEMIS-1132) Creating an AMQP Receiver when
security is configured can hang or return wrong error type
[ https://issues.apache.org/jira/browse/ARTEMIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated ARTEMIS-1132:
----------------------------------
Description:
When creating an AMQP receiver and the broker is configured with security the attach process can hang in the case where the queue does not exist and the user does not have permission to create said queue. The broker doesn't handle the exception thrown from the addressQuery operation and the exception thrown is handled incorrectly leading to no response being sent to the link attach request.
In some other cases where the receiver can create the queue but not consume from or browse the queue etc the broker sets the wrong error condition on the resulting attach response 'failed' instead of sending "amqp:unauthorized-access". This can result in clients not seeing the correct error response such as in Qpid JMS where a JMSSecurityException is expected but instead a vague JMSException is thrown. This happens during the creation of Temporary Destination when a dynamic node is requested as well.
was:
When creating an AMQP receiver and the broker is configured with security the attach process can hang in the case where the queue does not exist and the user does not have permission to create said queue. The broker doesn't handle the exception thrown from the addressQuery operation and the exception thrown is handled incorrectly leading to no response being sent to the link attach request.
In some other cases where the receiver can create the queue but not consume from or browse the queue etc the broker sets the wrong error condition on the resulting attach response 'failed' instead of sending "amqp:unauthorized-access". This can result in clients not seeing the correct error response such as in Qpid JMS where a JMSSecurityException is expected but instead a vague JMSException is thrown.
> Creating an AMQP Receiver when security is configured can hang or return wrong error type
> -----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-1132
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1132
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.0.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 2.next
>
>
> When creating an AMQP receiver and the broker is configured with security the attach process can hang in the case where the queue does not exist and the user does not have permission to create said queue. The broker doesn't handle the exception thrown from the addressQuery operation and the exception thrown is handled incorrectly leading to no response being sent to the link attach request.
> In some other cases where the receiver can create the queue but not consume from or browse the queue etc the broker sets the wrong error condition on the resulting attach response 'failed' instead of sending "amqp:unauthorized-access". This can result in clients not seeing the correct error response such as in Qpid JMS where a JMSSecurityException is expected but instead a vague JMSException is thrown. This happens during the creation of Temporary Destination when a dynamic node is requested as well.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)