Hi, Looks like the issue you are facing relates to temporary queues which display different behaviors in different JMS implementations.
The simple workaround as Claus pointed out is to use a named replyTo queue which is then persisted and outlives the recycling of the container/broker since it is cached automatically to persistent store. As for how to do this it can be added as a query parameter on the JMS URI as follows. "jms:queue:foo?replyTo=bar" Any responses to messages sent to queue foo will be sent to the queue called bar. Hope this helps. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com http://fusesource.com Blog: http://opensourceknowledge.blogspot.com http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Routes-throws-TimeOutException-after-ESB-restart-tp3229609p3231467.html Sent from the Camel - Users mailing list archive at Nabble.com.
