You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Stefan Kok <st...@centilliard.io> on 2022/10/10 10:20:18 UTC
ExchangeTimedOutException
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(OcepService
.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
Re: ExchangeTimedOutException
Posted by ski n <ra...@gmail.com>.
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 <st...@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 <cl...@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
> > > <st...@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
> > >
>
>
Re: ExchangeTimedOutException
Posted by Stefan Kok <st...@centilliard.io>.
Hi Wilken
Thank you for clarifying.
Stefan
On Mon, 2022-10-10 at 21:55 +0000, Wilken Marci J wrote:
> 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 <st...@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%7
> > C65
> > 8e63e88d39499c8f4813adc9452f4c%7C0%7C0%7C638010022016605912%7CUnkno
> > wn%
> > 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> > CJX
> > VCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3z8h74IALlh9ode4pzPbAphjjYCz%2
> > BQ3
> > 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
> > <cl...@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
> > > <st...@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(Oce
> > > > pS
> > > > 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%7C658e63e88d39499c8f4813adc94
> > > 52f4c%7C0%7C0%7C638010022016605912%7CUnknown%7CTWFpbGZsb3d8eyJWIj
> > > oiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C30
> > > 00%7C%7C%7C&sdata=WojJtU9A3egsk%2BVgSiowU8KTwFb1T43ON9vSlDcos
> > > G8%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
> > >
>
RE: ExchangeTimedOutException
Posted by Wilken Marci J <MA...@dhsoha.state.or.us.INVALID>.
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 <st...@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 <cl...@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
> > <st...@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
> >
Re: ExchangeTimedOutException
Posted by Stefan Kok <st...@centilliard.io>.
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 <cl...@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
> > <st...@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
> >
Re: ExchangeTimedOutException
Posted by ski n <ra...@gmail.com>.
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 <cl...@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 <st...@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(OcepService
> > .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
>
Re: ExchangeTimedOutException
Posted by Stefan Kok <st...@centilliard.io>.
On Mon, 2022-10-10 at 13:27 +0200, Stefan Kok wrote:
The reason why the second call to the route failed is that my code did
not update the rerence to the second exchang's exchange asyncCallback
i.e I used the previous asyncCallback.
> Hi Claus
>
> Thank you for the response.
>
> Background:
>
> We trying to translate between REST and Websockets (io.socket
> library)
> with a custom component in development.
>
>
> Calling the route:
>
> Exchange exchange = ExchangeBuilder
> .anExchange(producerTemplate.getCamelContext())
> .withPattern(ExchangePattern.InOut)
> .withBody(jsonNode)
> .build();
>
> CompletableFuture<Exchange> future =
> producerTemplate.asyncSend(EndPointUri.SEDA_START_END_POINT,
> exchange);
>
> The route is configured as follows:
> @Bean
> public RoutesBuilder ChangeAgentState() {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from(EndPointUri.SEDA_START_END_POINT)
> .routeId("ChangeAgentState")
> .process(new ChangeAgentStateProcessor())
> .to(cloudConfigClient.getWssUrl())
> .log(LoggingLevel.TRACE,"${body}");
> }
> };
>
> ChangeAgentStateProcessor converts the exchange message object from
> JsonNode to EventDto ( We will return EventDto to the caller)
>
> The first time the route is called the expected EventDto is received.
> The second time I call the route the object never arrives as per the
> exception below.
>
> Stefan
>
>
>
>
> On Mon, 2022-10-10 at 12:33 +0200, Claus Ibsen 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
> > <st...@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
> > > er
> > > vice
> > > .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
> > >
> >
> >
>
Re: ExchangeTimedOutException
Posted by Stefan Kok <st...@centilliard.io>.
Hi Claus
Thank you for the response.
Background:
We trying to translate between REST and Websockets (io.socket library)
with a custom component in development.
Calling the route:
Exchange exchange = ExchangeBuilder
.anExchange(producerTemplate.getCamelContext())
.withPattern(ExchangePattern.InOut)
.withBody(jsonNode)
.build();
CompletableFuture<Exchange> future =
producerTemplate.asyncSend(EndPointUri.SEDA_START_END_POINT, exchange);
The route is configured as follows:
@Bean
public RoutesBuilder ChangeAgentState() {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
from(EndPointUri.SEDA_START_END_POINT)
.routeId("ChangeAgentState")
.process(new ChangeAgentStateProcessor())
.to(cloudConfigClient.getWssUrl())
.log(LoggingLevel.TRACE,"${body}");
}
};
ChangeAgentStateProcessor converts the exchange message object from
JsonNode to EventDto ( We will return EventDto to the caller)
The first time the route is called the expected EventDto is received.
The second time I call the route the object never arrives as per the
exception below.
Stefan
On Mon, 2022-10-10 at 12:33 +0200, Claus Ibsen 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
> <st...@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(OcepSer
> > vice
> > .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
> >
>
>
Re: ExchangeTimedOutException
Posted by Claus Ibsen <cl...@gmail.com>.
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 <st...@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(OcepService
> .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