Hi,
In your stack trace I see NLP in CXF client call to endpoint
{http://www.globustravel.com/Services}GlobusTravel.
Looks like that Camel exchange is null in DefaultConsumer.doneUoW(). My guess
is that camel routes route finished early as async client returns response from
the remote service.
Could you replace this remote call to dummy and check if the problem persist?
Regards,
Andrei.
> -----Original Message-----
> From: Farkas Lajos [mailto:[email protected]]
> Sent: Dienstag, 14. Juni 2016 09:40
> To: [email protected]
> Subject: CXF Timeout problem
>
> Hello cxf users,
>
> I have a soap webservice, which is the entry point for a route, and from that
> route a second route is called, where a long processing operation is executed
> (40 seconds).
>
> If i call the second route with <to
> uri="seda:IN_ChildRoute?timeout=1000000">, then the webservice execution
> takes 40 seconds, and the proper response is returned.
>
> If i call the second route with <to
> uri="activemq:queue:IN_ChildRoute?requestTimeout=1000000">, then the
> webservice execution takes 30 seconds, returns an "Fault occurred while
> processing." error response. The route continues it's execution normally, so
> is
> not stopped.
>
> Also it seems that when using activeMQ, CXF throws an error after 30 seconds.
>
>
> I cannot use seda, as i have multiple processes from different contexts,
> on different servers running, so i need to use activeMQ.
>
> Thank you.
>
>
