[jira] [Created] (DISPATCH-1173) Exceptions handling

["Olivier VERMEULEN (JIRA)" <ji...@apache.org>]

Olivier VERMEULEN created DISPATCH-1173:
-------------------------------------------

             Summary: Exceptions handling
                 Key: DISPATCH-1173
                 URL: https://issues.apache.org/jira/browse/DISPATCH-1173
             Project: Qpid Dispatch
          Issue Type: Improvement
    Affects Versions: 1.3.0
            Reporter: Olivier VERMEULEN


We are using the Dispatch-Router 1.3.0, Broker-J 7.0.3 and Qpid JMS 0.11.1

For the same use case, the exception we get from the dispatch-router is much less explicit than the one we get when we connect to the broker directly.

 

For example when sending a message to a topic that does not exist.
 * Through the broker:

javax.jms.InvalidDestinationException: Could not find destination for target 'Target\{address=unknownDestination,durable=none,expiryPolicy=session-end,dynamic=false,capabilities=[topic]}' [condition = amqp:not-found]
 * Through the dispatch-router (defaultDistribution set to unavailable):

javax.jms.InvalidDestinationException: Node not found [condition = amqp:not-found]

 

Another example when sending a message bigger than the max_message_size set on the broker:
 * Through the broker:

javax.jms.JMSException: delivery '\x00' exceeds max-message-size 10240 [condition = amqp:link:message-size-exceeded]
 * Through the dispatch-router:

javax.jms.JMSException: Delivery failed: failure at remote

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org