Hi Ravi,

You should use set timeouts on the outgoing CXF invocations, where the sum
of the CXF timeouts is a tad lower than the timeout you set on the SEDA
call to commonRoute. I call this the "cascading timeouts" pattern.

So if timeout(webservice1) + timeout(webservice2) + timeout(webservice3) =
10000ms, you can turn direct:commonRoute into a SEDA endpoint and set the
"timeout" option of the SEDA producer to 11000ms, for example.

Here's an example that shows how to set timeouts on CXF producers [1].

[1]
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/resources/org/apache/camel/component/cxf/cxfConduitTimeOutContext.xml
.

Regards,

*Raúl Kripalani*
Apache Camel Committer
Enterprise Architect, Program Manager, Open Source Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk <http://twitter.com/raulvk>

On Fri, Oct 26, 2012 at 5:38 AM, ravi.4indra <[email protected]> wrote:

> Thanks for your reply!!
> common route makes a series of webservices calls
>
> like
>
> to(cxf://webservice1)
> .bean(processresponse)
> to(cxf://webservice2)
> .bean(processresponse)
> to(cxf://webservice3)
> .bean(processresponse)
>
> Thanks
> Ravi
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Timeout-on-a-route-tp5721576p5721581.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Reply via email to