It took us a few day to respond as the third party server was down.
Anyway after adding logging to the project we still couldn't find any
obvious trace for sending the message twice.
As mentioned soapUI client and the same camel project with HttpClient
library don't exhibit the same issue which is
y obvious setting on the cxf configuration or the HTTP
> Conduit to prevent this from happening.
> Any suggestions on what may cause a 'NoHttpResponse' error to trigger
> sending a second message will be appreciated.
>
>
>
> --
> View this message in context:
>
dn't find any obvious setting on the cxf configuration or the HTTP
Conduit to prevent this from happening.
Any suggestions on what may cause a 'NoHttpResponse' error to trigger
sending a second message will be appreciated.
--
View this message in context:
http://camel.465427.n5.nabble.com/
