I don't think we can configure HttpConduit do it - if it were possible then it would probably lead to 'hiding' the issues like the ones you are seeing with CXF 2.2.7. As suggested in the other emails, try upgrading to the newer CXF. The other question: do you use a standalone Jetty container (you refer to server.xml, so probably yes) ? Can it be something to do with the way it is configured ? Assuming it is a standalone Jetty container, please try narrowing down the problem as follows, after upgrading to the newer CXF :-), : - remove the configuration completely and see if the issue persists - update to the newer Jetty and see if the issue persists
Let us know how it goes please Sergey -- View this message in context: http://cxf.547215.n5.nabble.com/Automatic-retry-of-HTTP-Request-upon-Socket-error-tp5726984p5726999.html Sent from the cxf-user mailing list archive at Nabble.com.
