Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.3.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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

       

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              overmeulen Olivier VERMEULEN
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: