We came across the following issue when using the Camel CXF component to invoke a SOAP request with Payload mode over HTTPS on a third party service.
The third party server provides two endpoints primary and secondary. As part of certifying our system with this service (fail over test), we were required to invoke a test request on the primary (which failed with No HTTP Response error). The Camel client sent one message (as observed on our Camel Trace log) but the server received two requests. We used soapUI client to invoke the same test server just to confirm that the server register one request only. Note that the 'Redelivery Policies' were configured with 'maximumRedeliveries' of 0. We ended up replacing the "cxf://.." endpoint with a 'processor' with Apache HTTPClient and this solve the duplicate message being sent. We couldn'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/CXF-SOAP-Message-Sent-from-a-Camel-Client-Twice-When-No-HTTP-Response-Received-tp5771010.html Sent from the Camel - Users mailing list archive at Nabble.com.
