You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/15 01:23:30 UTC
[jira] [Resolved] (AMQNET-361) ActiveMQ Client should attempt to
create NMS exceptions for Broker ExceptionResponse commands that contains
exceptions
[ https://issues.apache.org/jira/browse/AMQNET-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-361.
---------------------------------
Resolution: Fixed
fixed in trunk
> ActiveMQ Client should attempt to create NMS exceptions for Broker ExceptionResponse commands that contains exceptions
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-361
> URL: https://issues.apache.org/jira/browse/AMQNET-361
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.5.0, 1.5.1, 1.5.2
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.6.0
>
>
> When receiving an ExceptionResponse from the Broker the client currently just creates a local BrokerException and passes that along. In some cases the ExceptionClass field in the ExceptionResponse's BrokerError object can match an NMS exception type such as a SecurityException or InvalidSelectorException. We should attempt to map those exception class names into NMS Exception instances with the supplied message value in order to provide more detailed exception information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira