[
https://issues.apache.org/jira/browse/CAMEL-14307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Vanderhallen updated CAMEL-14307:
---------------------------------------
Description:
The Camel RabbitMQ endpoint does not allow to set an empty routing key when
configuring a dead letter exchange:
{quote}[error] <0.664.0> Channel error on connection <0.649.0>
(192.168.224.3:55000 -> 192.168.224.2:5672, vhost: '/', user: 'rabbitmq'),
channel 1:
operation queue.declare caused a channel exception precondition_failed:
inequivalent arg 'x-dead-letter-routing-key' for queue 'testqueue' in vhost
'/': received the value 'undefined' of type 'void' but current is none
{quote}
This is required if you want to keep the original routing key on the message
when it is sent to the dead letter queue.
When setting the deadLetterRoutingKey property to an empty value, the error
doesn't appear but the original routing is lost.
was:
The Camel RabbitMQ endpoint does not allow to set an empty routing key when
configuring a dead letter exchange:
{{[error] <0.664.0> Channel error on connection <0.649.0> (192.168.224.3:55000
-> 192.168.224.2:5672, vhost: '/', user: 'rabbitmq'), channel 1:
operation queue.declare caused a channel exception precondition_failed:
inequivalent arg 'x-dead-letter-routing-key' for queue 'testqueue' in vhost
'/': received the value 'undefined' of type 'void' but current is none}}
This is required if you want to keep the original routing key on the message
when it is sent to the dead letter queue.
When setting the deadLetterRoutingKey property to an empty value, the error
doesn't appear but the original routing is lost.
> camel-rabbitmq - unable to set empty routing key when declaring DLX
> -------------------------------------------------------------------
>
> Key: CAMEL-14307
> URL: https://issues.apache.org/jira/browse/CAMEL-14307
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
> Affects Versions: 2.22.1, 2.24.2
> Reporter: Robin Vanderhallen
> Priority: Major
>
> The Camel RabbitMQ endpoint does not allow to set an empty routing key when
> configuring a dead letter exchange:
> {quote}[error] <0.664.0> Channel error on connection <0.649.0>
> (192.168.224.3:55000 -> 192.168.224.2:5672, vhost: '/', user: 'rabbitmq'),
> channel 1:
> operation queue.declare caused a channel exception precondition_failed:
> inequivalent arg 'x-dead-letter-routing-key' for queue 'testqueue' in vhost
> '/': received the value 'undefined' of type 'void' but current is none
> {quote}
> This is required if you want to keep the original routing key on the message
> when it is sent to the dead letter queue.
> When setting the deadLetterRoutingKey property to an empty value, the error
> doesn't appear but the original routing is lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
