Thanks a lot for your suggestion. The problem as I understand it is, there is a connection between sender and receivers parties, but its seems that camel acts on an old session.
Another thing is: The "the out message was ...." get into the trace in few milliseconds. [2017-02-24 11:10:57,068] [INFO ] -- before [2017-02-24 11:10:57,079] [ERROR] -- The OUT message was not received within : 30000 millis. [2017-02-24 11:10:57,082] [INFO ] -- after I am not sure when camel starts to wait for a reply from the receiver. Secondly the message that has not been delivered is still in the Queue (ActiveMQ). So, after restart of application the very same message is sent out. Anyway, I will discuss your points with the developer. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-route-does-not-reconnect-tp5794411p5794441.html Sent from the Camel - Users mailing list archive at Nabble.com.
