I am pretty sure, since I traced the message at all the 3 hops and ensured it has the same correlation id 1. tracer on the producer side 2. On the AMQ console 3. tracer on the consumer side
It might be a misleading exception, also, the same thing works if I use an instantiated connection factory versus the injected one ( from resource adapter ) -- View this message in context: http://camel.465427.n5.nabble.com/JMS-message-with-Inout-pattern-tp5787336p5787433.html Sent from the Camel - Users mailing list archive at Nabble.com.
