[ https://issues.apache.org/jira/browse/DISPATCH-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ganesh Murthy updated DISPATCH-1173: ------------------------------------ Labels: usability (was: ) > 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, 1.8.0 > Reporter: Olivier VERMEULEN > Priority: Major > Labels: usability > > 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 (v8.3.2#803003) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org