When you need to set the exchange pattern explicit:

from("direct:foo")
  .setExchangePattern(ExchangePattern.InOut)
  .to("jms:queue:cheese");

I think when using an async producer template this pattern is automatically
set.

When you want to debug your route, you could set it as:


 from(EndPointUri.SEDA_START_END_POINT)
     .routeId("ChangeAgentState")
     .to("log:com.mycompany.changeagent?showAll=true&multiline=true")
     .process(new ChangeAgentStateProcessor())
     .to("log:com.mycompany.changeagent?showAll=true&multiline=true")
     .to(cloudConfigClient.getWssUrl())
     .to("log:com.mycompany.changeagent?showAll=true&multiline=true");

It's interesting (when possible) to also check the log on the server side.

Raymond




On Mon, Oct 10, 2022 at 2:36 PM Stefan Kok <stefan....@centilliard.io>
wrote:

> 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://camel.apache.org/manual/exchange-pattern.html
> >
> > 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
> > > -----------------
> > > http://davsclaus.com @davsclaus
> > > Camel in Action 2: https://www.manning.com/ibsen2
> > >
>
>

Reply via email to