Yes, use setMessage() on return. I ran into this a while back. Not all message processes have an in and an out. If the message process doesn't create an out by using setOut it created a new blank message and you loose everything from the original message.
-----Original Message----- From: Stefan Kok <stefan....@centilliard.io> Sent: Monday, October 10, 2022 5:36 AM To: users@camel.apache.org Subject: Re: ExchangeTimedOutException Think twice before clicking on links or opening attachments. This email came from outside our organization and might not be safe. If you are not expecting an attachment, contact the sender before opening it. Thanks, Raymond On the return, I am not using the setOut method but the setMessage as setOut has been deprecated. It is my understanding that we should use setMessage instead of setOut. Stefan On Mon, 2022-10-10 at 12:43 +0200, ski n wrote: > To enhance the answer of Claus: > > An exchange in Camel has two types: > > 1) InOnly > 2) InOut > > See: > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcame > l.apache.org%2Fmanual%2Fexchange-pattern.html&data=05%7C01%7CMARCI > .J.WILKEN%40dhsoha.state.or.us%7C8a8b0830f3514151378908daaabc12ad%7C65 > 8e63e88d39499c8f4813adc9452f4c%7C0%7C0%7C638010022016605912%7CUnknown% > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJX > VCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3z8h74IALlh9ode4pzPbAphjjYCz%2BQ3 > L4zC51nuaMHs%3D&reserved=0 > > With the first type of exchange, "InOnly", the exchange is an event > message (also called 'fire and forget' or 'one-way)'. You will never > see the > warning/error: "The OUT message was not received within: 60000 > millis". > > With the second type of exchange, "InOut", the exchange is > request/reply. > Thus, when the reply (OUT) doesn't arrive on time it gives this error. > > It thus means: > > "It didn't arrive within the configured timeout". > > By default, the timeout is configured as, 20000 ms (20 seconds), but > this can be set differently for a specific component. > > Raymond > > > > > On Mon, Oct 10, 2022 at 12:33 PM Claus Ibsen <claus.ib...@gmail.com> > wrote: > > > It says that the message did not arrive, and that a timeout was > > triggered because of that. > > > > What kind of messaging protocol do you use? JMS, http, etc? > > > > On Mon, Oct 10, 2022 at 12:20 PM Stefan Kok > > <stefan....@centilliard.io> > > wrote: > > > > > Hi All > > > > > > I am having great difficulty making sense of the below log entry: > > > > > > 10-10-2022 11:53:11.497 WARN [ForkJoinPool.commonPool-worker-2] > > > com.experflow.service.OcepService.lambda$changeAgentState$3(OcepS > > > ervice > > > .java:115) - Exception Message: > > > org.apache.camel.ExchangeTimedOutException: The OUT message was > > > not received within: 60000 millis. Exchange[8AFA941458EDDAE- > > > 0000000000000002] > > > > > > What is the meaning? > > > > > > 1) The message arrived late but it did arrive. > > > 2) The message did not arrive at all. > > > > > > Thank you in advance > > > > > > > > > -- > > Claus Ibsen > > ----------------- > > https://gcc02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdav > > sclaus.com%2F&data=05%7C01%7CMARCI.J.WILKEN%40dhsoha.state.or.us > > %7C8a8b0830f3514151378908daaabc12ad%7C658e63e88d39499c8f4813adc9452f4c%7C0%7C0%7C638010022016605912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=WojJtU9A3egsk%2BVgSiowU8KTwFb1T43ON9vSlDcosG8%3D&reserved=0 > > @davsclaus Camel in Action 2: > > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.manning.com%2Fibsen2&data=05%7C01%7CMARCI.J.WILKEN%40dhsoha.state.or.us%7C8a8b0830f3514151378908daaabc12ad%7C658e63e88d39499c8f4813adc9452f4c%7C0%7C0%7C638010022016605912%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GhWgs%2BFvC8eyrN4QNQ8AiujadlBAudv2ws4Niu9nJKc%3D&reserved=0 > >
