I looked at the source going back a few years and at one point there was some axis2 java test coverage for commons httpclient 3.x features using HttpMethodParams.RETRY_HANDLER.
When we converted over to httpclient 4.x, we redid EchoRawMTOMFaultReportTest. See the history for testEchoFaultSync() and how it turned out now. However, the support of HTTP_METHOD_PARAMS was removed in the migration to 4.x. Anyways, putting disableAutomaticRetries() before build() at the end of HTTPSenderImpl should make it do zero retries. If that works for you, I suggest creating a Jira issue and a patch for supporting zero retries. Robert On Thu, Oct 14, 2021 at 11:14 PM Nugent, Rob <rob.nug...@nttdata.com> wrote: > Hello All, > > > > Prior to Axis2/J 1.8.0, I have been using the technique described at the > following URL to disable retries with the Axis client: > > > > > https://stackoverflow.com/questions/2211578/axis2-how-to-set-connection-retry > > > > Now, this technique uses classes (e.g. HttpMethodParams) that are part of > Apache Commons HttpClient 3.x. So this technique doesn’t work with Axis2/J > 1.8.0. > > > > Does anyone know how to disable retries with Axis2/J 1.8.0 please ? I’ve > dug quite deep into this, including into the Axis source code, but there > isn’t an obvious way to achieve this. > > > > Thanks, > > Rob > > > > > > *Robert Nugent* | Software Development > > rob.nug...@nttdata.com > > *NTT DATA* | *nttdataservices.com <http://nttdataservices.com>* | > *@nttdataservices* > > Consulting | Industry Solutions | Cloud & Digital Services > > NTT DATA Services UK Limited > > > Disclaimer: This email and any attachments are sent in strictest > confidence for the sole use of the addressee and may contain legally > privileged, confidential, and proprietary data. If you are not the intended > recipient, please advise the sender by replying promptly to this email and > then delete and destroy this email and any attachments without any further > use, copying or forwarding. >
