After a lot of testing I have determined the cause of an issue I am having when using 2 different activeMQ JMS endpoints in the same route. Apparently after the first JMS queue is used, the message back will have a bunch of headers set such as JMSCorrelationId, messageId, JMSMessageId, etc.
Now it seems that when the second JMS queue is called the values on the exchange for these headers is used which invariably causes message collisions. My question is, is there a way to remove headers, or with regards to multiple JMS queues to ensure the correlation and message IDs are always originated with respect to the proper queue and message? -- View this message in context: http://camel.465427.n5.nabble.com/JMS-Header-Issue-tp5129929p5129929.html Sent from the Camel - Users mailing list archive at Nabble.com.