Well the scenario is that the producer is one of many temporary threads but the reply message must always be consumed even after the producer thread has stopped. So the trick with creating another producer is being able to make it a permanent thread (janitor) that processes all reply messages. So I think the answer is very close to what you are suggesting.
I'm thinking that if I get the producer thread to listen to the return thread and then post the return endpoint to the janitor then it kind of does what I need. The problems then are ones of organising the sequence of events so that the message does not fall into the DLQ between the end of the in/out and the time that the janitor starts listening for the message. -- View this message in context: http://camel.465427.n5.nabble.com/How-do-I-avoid-using-the-dead-letter-queue-using-Camel-tp5730386p5730446.html Sent from the Camel - Users mailing list archive at Nabble.com.
