[
https://issues.apache.org/jira/browse/QPID-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13589951#comment-13589951
]
Rajith Attapattu commented on QPID-4608:
----------------------------------------
I have now added code to handle the TransportException and any RuntimeException
that could be thrown.
FailoverException is not thrown as it's a checked exception and not a runtime
exception.
> JMS client authorization failure throws JMSException instead of
> JMSSecurityException
> ------------------------------------------------------------------------------------
>
> Key: QPID-4608
> URL: https://issues.apache.org/jira/browse/QPID-4608
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.18, 0.20
> Reporter: Rajith Attapattu
> Assignee: Rajith Attapattu
> Priority: Minor
> Labels: jms, jmsexception
> Fix For: 0.21
>
>
> When ACLs doen't authorize a user to perform an action, Java client raises
> JMSException while JMSSecurityException should be raised.
> From the java docs for JMSSecurityException,
> "This exception must be thrown when a provider rejects a user name/password
> submitted by a client. It may also be thrown for any case where a security
> restriction prevents a method from completing."
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
