Are you sure the problem is on Camel's end? I've never seen such a
behaviour.
How long does the external service take to respond? Perhaps it cannot
handle concurrent requests? Or it responds badly?
What's the exception seen by Camel?
To aid investigation, I suggest you monitor de HTTP traffic using
Wireshark, tcpdump or a proxy.
Regards,
Raúl.
On 22 Apr 2013 13:37, "Smith-John" <mich...@gmail.com> wrote:
> Just to check if I understand you right:
>
> Do you mean, my route should look like
>
> from("cxf:XXX?wsdlURL=YYY&...")....to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&...&synchronous=true");
> instead of
>
> from("cxf:XXX?wsdlURL=YYY&...")....to(...)...to("cxf:${header[ReplyTo]}?wsdlURL=YYY&...");
> ?
>
> I tried this, but cxf producer nevertheless isn't capable to send a message
> every 2 seconds for example.
>
> Regards.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/cxf-producer-needs-a-break-tp5730612p5731249.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
