cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

PI 731 - HTTP (error code: 401 , error text: ICM_HTTP_CONNECTION_BROKEN)

jorge_velasquez
Contributor
0 Likes
4,128

Hi Experts,

We are facing an issue when trying to go from file to proxy

INTERNAL">CLIENT_RECEIVE_FAILED

<SAP:P1>401</SAP:P1>

<SAP:P2>ICM_HTTP_CONNECTION_BROKEN</SAP:P2>

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--  Empfängergruppierung

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>XIServer</SAP:Category>

  <SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>

  <SAP:P1>110</SAP:P1>

  <SAP:P2>HTTPIO_PLG_CANCELED</SAP:P2>

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText />

  <SAP:Stack>Error while receiving by HTTP (error code: 110 , error text: HTTPIO_PLG_CANCELED)</SAP:Stack>

  <SAP:Retry>A</SAP:Retry>

  </SAP:Error>

We already change parameters:

rdisp/keepalive_timeout 300

rdisp/max_wprun_time 3600

icm/server_port_0  PROT=HTTP,PORT=50200,TIMEOUT=60,PROCTIMEOUT=1200

icm/HTTP/max_request_size_KB  -1

Any clue?

View Entire Topic
americo_goncalvesqualho
Product and Topic Expert
Product and Topic Expert
0 Likes

ICM_HTTP_CONNECTION_BROKEN means that the communication partner unexpectedly closed the connection.

One possible cause for the error is that the client is sending HTTP requests to an HTTPS port. In this case the server simply closes the connection.

In many cases the cause of the error lies on the server side.

Please check in the ICM trace file dev_icm which server closes the connection, there should be a corresponding ERROR trace entry.

Then please validate that the port the request is sent to is a valid HTTP or HTTPS port depending on the protocol being used.

If this is the case you need to check for the problem on the server side.