000035606 - RSA Adaptive Authentication (OnPrem) 7.1 P6 - Troubleshoot "org.apache.axis2.AxisFault: Connection reset by peer" error

Document created by RSA Customer Support Employee on Dec 1, 2017
Version 1Show Document
  • View in full screen mode

Article Content

Article Number000035606
Applies ToRSA Product Set: Adaptive Authentication (OnPrem)
RSA Product/Service Type: Adaptive Authentication (OnPrem)
RSA Version/Condition: 7.1 P6
IssueThis error appears in the aa_server.log:

2017-09-29 09:12:06,546 ERROR [[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [] [] [org.apache.axis2.transport.http.CommonsHTTPTransportSender] - <Connection reset by peer>
org.apache.axis2.AxisFault: Connection reset by peer
    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
    at org.apache.axis2.transport.http.SOAPMessageFormatter.writeTo(SOAPMessageFormatter.java:78)
Caused by: com.ctc.wstx.exc.WstxIOException: Connection reset by peer
    at com.ctc.wstx.sw.BaseStreamWriter.flush(BaseStreamWriter.java:278)
    at org.apache.axiom.util.stax.wrapper.XMLStreamWriterWrapper.flush(XMLStreamWriterWrapper.java:50)
    ... 34 more
Caused by: java.io.IOException: Connection reset by peer
    at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)

CauseThe error message "Connection reset by peer" appears if the web services client was waiting for a SOAP response from the remote web services provider and the connection was closed prematurely.
One of the most common causes for this error is a network component closing the connection. The component that closes the connection can be found by capturing and analyzing an IP trace. This component can be either a Firewall, a load balancer or any other device that takes part in the connection.
Other possible causes are:
  • Resources limitations on the server side (e.g: out of memory)
  • Process killed
  • Overload on the server due to a high amount of traffic
  • Connection closed by the ws-client before receiving the response 
ResolutionThis is not an error of the AA application itself but an indicator that the response of the server was not received by the client.
WorkaroundThe network components have to be reviewed to make sure everything is in place and working right and the response from the web service call is properly received by the client.