[
https://issues.apache.org/jira/browse/ARTEMIS-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989252#comment-15989252
]
ASF subversion and git services commented on ARTEMIS-1132:
----------------------------------------------------------
Commit 19a640db3a180db65592bb2d87c1d3193eada306 in activemq-artemis's branch
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=19a640d ]
ARTEMIS-1132 return security errors instead of generic failed
When creating some AMQP resources (senders, receivers, etc) the broker
can return an error of 'failed' instead of the security error that is
expected in these cases. In the case of a receiver being created and
a security error happening the broker fails to send back a response
causing the client to hang waiting for an attach response.
> Creating an AMQP resources 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)
