When the Activator and Interchange applications encounter a blocked connection, they will automatically try to re-establish the connection to the trading partner's HTTP server.

However, these applications must receive a valid 'Connection Failed' error message before they will retry to establish the connection. If the status code returned by the partner's HTTP server is not a valid HTTP response as specified by the interoperability standards, these applications will not try to re-establish the connection out to the partner.

Activator and Interchange will not attempt to re-establish the connection because re-connecting will probably result in the same error. The applications also do not want to overwhelm the partner's HTTP server with connection requests. An exception to this is the '503 Service Unavailable' response. By default, the applications will automatically try to re-establish the connection when they receive a '503 Service Unavailable' response.

To configure Activator and Interchange so they will automatically try to re-establish the connection when they receive other HTTP error responses, please follow the instructions below.

Create a file in the conf directory with this name.
retryablehttperrorresponses.xml

The format of the file is simple. Each error code that you would like to retry is included as a XML element in the file. This example will cause the applications to retry on

<HttpResponseCodes>
  <Code>503</Code>
  <Code>400</Code>
  <Code>599</Code>
</HttpResponseCodes>

After you have created or modified this file, the Activator and Interchange applications must be stopped and restarted to update this change to the system.