[AMQNET-361] ActiveMQ Client should attempt to create NMS exceptions for Broker ExceptionResponse commands that contains exceptions

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.5.0, 1.5.1, 1.5.2
• Fix Version/s: 1.6.0
• Component/s: ActiveMQ
• Assignee: Timothy A. Bish
• Reporter: Timothy A. Bish
• Created: 14/Dec/11 20:53
• Updated: 02/May/13 02:29
• Resolved: 15/Dec/11 00:23

Description

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.

Issue Links

• depends upon: AMQNET-360 ActiveMQ client ResponseCorrelator doesn't handle ExceptionResponse commands correctly.
• is depended upon by: AMQNET-362 ActiveMQ ConnectionStateTracker should rollback transactions that have a pending Commit when a Failover occurs.
• is depended upon by: AMQNET-363 ActiveMQ client should throw the InvalidClientIDException from CheckConnected when broker reports the Id as invalid.
• is related to: AMQNET-389 Implementing a catch for an empty catch clause in the Connection.cs CheckConnected() method at line 777.