Error-Code: 108 - CLIENT_RECEIVE_FAILED

[former_member246510]

Hello,

I have set up the following synchronous scenario:

R/3 <-> ABAP-Proxy <-> XI <-> JDBC <-> ORACLE

The whole thing works fine as long as the requests don't get to big. But now I have to fetch about 150.000 records from the USA to Germany. The thing will last approximately 4-5 hours. The data-volume will be about 50 to 60 mb (as csv-file). As xml-file ??? Maybe >150 mb.

I have liftet up all necessary timeouts to 36000 sec. If I try to get the 150.000 records I get after a bit more than an hour this error in the XI:

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

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

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

<SAP:P1>108</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Fehler beim Empfangen per HTTP (Fehlercode: 108, Fehlertext: )</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

And this is the end of the trace file:

<Trace level="3" type="T">HTTP-client: sending http-request...</Trace>

<Trace level="3" type="T">HTTP-client: request sent</Trace>

<Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>

<Trace level="3" type="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>

</Trace>

</Trace>

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST">

<Trace level="3" type="T">Persisting message Status = 023</Trace>

<Trace level="3" type="T">Message version 006</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</Trace>

</Trace>

<Trace level="1" type="T">SystemError message generated. Guid: 43019BD1F29A007F020000000A180A87</Trace>

<Trace level="1" type="T">Error during execution of message : 43015B3EDCA300A0020000000A180A28</Trace>

<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 43015B3EDCA300A0020000000A180A28</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="3" type="T">Persisting message Status = 023</Trace>

<Trace level="3" type="T">Message version 000</Trace>

<Trace level="3" type="T">Pipeline CENTRAL</Trace>

</SAP:Trace>

</SOAP:Header>

Maybe has anybody an idea ??? - thanks - werner

[former_member246510]

Problem solved.

Many thanks to all !

[former_member209955]

Hi Werner,

Can you please share the solution?

I'm getting the same error.

Regards,

Amit Bharti

[Former Member]

Hi Werner,

Did you manage to resolve this issue, if so could you please let me know. I am having exactly the same error message,

--Start

<SAP:Category>XIAdapter</SAP:Category>

<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>

<SAP:P1>108</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>HTTP client. Code 108 reason</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

End.

THank you.

Warm Regards.

Ranjan

[Former Member]

This can mean that receiving system, e.g. HTTP endpoint is down/not responding.

It is very typical for ABAP proxy, SOAP scenarios when passing message to receiving system.

In case of ABAP proxy as receiving system, you should check whether:

a) ICM is up and running in corresponding business system (transaction SMICM)

b) HTTP destination (e.g. host, service) is correctly defined corresponding communications channel

In case of SOAP it is basically the same only of course you will have to check specific WebServer which is providing SOAP service (most likely it will not be an ABAP system).

[MichalKrawczyk]

Hi Werner,

take a look at this guide:

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/3.0/sap exchange infrastructure tuning guide xi 3.0.pdf

and check how big is your maximum HTTP request

Parameter:

icm/HTTP/max_request_size_KB

(Maximum size of HTTP request accepted by ICM)

does it have more then 150 mb?

if not try increasing it

Regards,

michal