That OUT message error is when you do request/reply over JMS (eg InOut) then the reply message was not sent back to the JMSReplyTo queue within those 30 seconds, and therefore Camel times out and fails.
The JMS component has options to set higher timeout and much more On Fri, Feb 24, 2017 at 3:48 PM, souciance <[email protected]> wrote: > Well the thing is the statement here: > > [org.apache.camel.ExchangeTimedOutException: The OUT message was not > received within: > > says that it got a time out issue and also at the end of the log there are > statements that indicate the the route seems to use the mina component to > send the data. But without looking at the code it is a bit hard to comment > with details. > > But in general I would say when you are sending data then: > 1. Either tell the developer to implement an error handler in the camel > route so that the route retries until it receives a connection again. > 2. Back out the message to a backout queue and manually retry after the > connection is up. You would need to implement this as well and probably > monitor that queue so you become aware of it. > 3. The error seems to indicate that the rollback fails because no message > was received within the 30 second time out value. Perhaps the developer can > do a try/catch the exception and set the original message on the body if > the route times out so the rollback can occur? > > But yeah without the code it is a bit hard to comment the details. > > On Fri, Feb 24, 2017 at 3:36 PM, Nader [via Camel] < > [email protected]> wrote: > >> I am not developer, but am a MQ-administrator. >> >> If you have a specific question about the code (I hope regarding the >> camel-route) then I will try to provide that to you, otherwise I have to >> get a developer involved into this discussion. >> >> Doesn't the trace indicate that the session is not timing out? The >> receiving application is closed. >> >> Is there anyway to set session time out for message delivery? >> >> Thanks in advance. >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> http://camel.465427.n5.nabble.com/Camel-route-does-not- >> reconnect-tp5794411p5794434.html >> To start a new topic under Camel - Users (activemq), email >> [email protected] >> To unsubscribe from Camel - Users, click here >> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=> >> . >> NAML >> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-route-does-not-reconnect-tp5794411p5794435.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
