You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Mahesh (Jira)" <ji...@apache.org> on 2020/01/26 10:44:00 UTC
[jira] [Created] (CAMEL-14441) Stomp connections are not
established when the queues have additional features
Mahesh created CAMEL-14441:
------------------------------
Summary: Stomp connections are not established when the queues have additional features
Key: CAMEL-14441
URL: https://issues.apache.org/jira/browse/CAMEL-14441
Project: Camel
Issue Type: Bug
Components: camel-stomp
Affects Versions: 3.0.0
Reporter: Mahesh
Fix For: Future
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:
# 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'}}
# Message broker creates a plain temporary queue while subscribing to an exchange
{{The additional parameters are all skipped}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)