Thinking about the problem in another way (and assuming request-reply on topic not possible) - how best to mark an exchange as incomplete until another JMS message has been received in another queue?
So I am thinking along the lines of having two routes: Route (1) sending JMS messages to topic, and not marking the exchange as complete until... Route (2) receives JMS ack message for the above on another predefined topic ? So a way to essentially block and wait after the message has been sent on Route (1), awaiting relevant event on Route (2), only then marking the exchange on Route (1) as complete. Any solution I can think of begins to get a bit ugly.. e.g spawning off a thread after JMS message has been sent to await ack, sending all acks being received on Route (2) to a concurrent cache, Route(1) checking the cache for ack after wait time etc. -- View this message in context: http://camel.465427.n5.nabble.com/JMS-replyTo-always-on-Queue-ignores-topic-in-dest-param-tp5773459p5775636.html Sent from the Camel - Users mailing list archive at Nabble.com.
