[CAMEL-14441] Stomp connections are not established when the queues have additional features

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0
• Component/s: camel-stomp
• Estimated Complexity: Unknown
• Assignee: Andrea Cosentino
• Reporter: Mahesh
• Created: 26/Jan/20 10:43
• Updated: 27/Jan/20 09:02
• Resolved: 27/Jan/20 09:02

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

 

Issue Links

• links to: GitHub Pull Request #3516