Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-14441

Stomp connections are not established when the queues have additional features

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.1.0
    • Component/s: camel-stomp
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      Stomp connections are not established when queues are configured with additional features

      Assume a queue created with additional features like x-dead-letter-exchange, x-dead-letter-routing-key, x-message-ttl, and so on..

      At present, only the destination and id attributes are set in Stomp frames while subscribing to a destination. Because of this:

      1. Message Broker throws an exception while subscribing to an existing queue
        operation queue.declare caused a channel exception precondition_failed: inequivalent arg 'xxx-xxx-xxx' for queue 'yyy' in vhost '/': received none but current is the value 'zzz-zzz' of type 'longstr'
      2. Message broker creates a plain temporary queue while subscribing to an exchange
        The additional parameters are all skipped

       

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                acosentino Andrea Cosentino
                Reporter:
                onlybytes Mahesh
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 20m
                  20m