bmcristi opened a new issue, #1733:
URL: https://github.com/apache/camel-kafka-connector/issues/1733
Hey, I am trying to figure out how can the message id and exchange id be
extracted in a kamelet and add them to the header of the kafka message.
Currently I see some headers which seem to be produced by RabbitMQ:
```
CamelHeader.__TypeId__ = com....model.Transaction
CamelHeader.CamelSpringRabbitmqContentEncoding = UTF-8
CamelHeader.CamelSpringRabbitmqContentType = application/json
CamelHeader.CamelSpringRabbitmqDeliveryTag = 3376
CamelHeader.CamelSpringRabbitmqExchangeName = my-exchange
CamelHeader.CamelSpringRabbitmqPriority = 0
CamelHeader.CamelSpringRabbitmqRedelivered = false
CamelHeader.CamelSpringRabbitmqRoutingKey = my-routing-key
CamelHeader.transactionType = my-transaction-type
CamelHeader.vendorCode = my-vendor
CamelHeader.x-first-death-exchange = my-exchange
CamelHeader.x-first-death-queue = my-queue
CamelHeader.x-first-death-reason = rejected
CamelHeader.x-match = all
```
And I would like to add 2 more regarding exchange id and message id (noticed
in an error that these are available_
```
[Worker-05438d3868ee8acfa] [2025-10-28 17:43:13,084] ERROR
[transactions|task-0] Failed delivery for (MessageId:
025B91CB6BEC07C-0000000000000023 on ExchangeId:
025B91CB6BEC07C-0000000000000023). Exhausted after delivery attempt: 1 caught:
....
```
So I am trying to get them to work in the kamelet, without luck.
```
steps:
- setHeaders:
headers:
- name: header.rabbitmq_message_id
simple: "${exchange.message.messageId}"
- name: header.rabbitmq_exchange_id
simple: "${exchangeId}"
- doTry:
steps:
- to: "kamelet:sink"
- process:
ref:
"#class:com.teststuff.camel.processor.ManualAckProcessor"
doCatch:
- exception: java.lang.Exception
steps:
- process:
ref:
"#class:com.teststuff.camel.processor.ManualNackProcessor"
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
