Unable to see the JMSMessageID that was routed by the JMS client in the Camel exchange
Issue
- In a Camel route, which is routing JMS Messages from one destination to another, the JMS client's JMS Message ID is not added to the Camel exchange.
- For example, consider this Camel Route:
<route id="route1">
<from id="from1" uri="jms:queue:QueueA"/>
<log message="Incoming message headers: ${headers}"/>
<log message="Incoming message body: ${body}"/>
<to uri="jms:queue:QueueB"/>
<log message="Incoming message headers: ${headers}"/>
<log message="Incoming message body: ${body}"/>
</route>
- In this example, the MessageExchange propagates the JMSMessageID created by the broker for QueueA.
Environment
- Red Hat Fuse 7.x
- Apache Camel 2.x/ 3.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.