CLIENT_RECEIVE_FAILED in xi xml monitor

[Former Member]

Hi, guys.

my scenario is ABAP Proxy->XI->SOAP. The information can send to XI, but during the sending process to XI, there is an error when call integration server.

the error information is :

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

<SAP:P1>400</SAP:P1>

<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>

and AdditionalText is listed below:

404 Resource not found

Partner not reached

-

---

Error: -20

Version: 7000

Component: ICM

Date/Time: Mon Apr 30 10:12:47 2007

Module: icxxconn_mt.c

Line: 2314

Server: eccd01_R3P_00

Error Tag:

Detail: Connection request from (9/45/0) to host: xiprd, service: 8000 failed (NIEHOST_UNKNOWN) AP-T9, U45, 600 QM, ids-5fc392252cf, 10:12:47, M0, W1, , 1/0

moreover see the listed information:

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>

<SAP:Timestamp type="begin" host="eccprd">20070430014744.464548</SAP:Timestamp>

</SAP:RunTimeItem>

- <SAP:RunTimeItem>

<SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>

<SAP:Timestamp type="end" host="eccd01">20070430005402.233584</SAP:Timestamp>

</SAP:RunTimeItem>

the time is too long between the begin and the end.

looking forward your ideas.

Thanks in advance.

Alex

[Former Member · Accepted solution]

Hi,

Is your XI server up?

Also, try to ping the XI server from the SAP server where the client proxy runs.

Unknown Host exception usually occurs when the server is down, or is inaccessible from sender system.

<i>Please award points if this solves the problem.</i>

Regards,

Puloma.

[Former Member · Accepted solution]

yes, the message can send to XI but there is this error during the process.

[Former Member · Accepted solution]

Hi,

What is the response of "ping xiprd" from sebder SAP system? Please paste here.

Also, paste the following URL in explorer and see what the response is:

http://<fully-qualified hostname>:80000/sap/xi/engine/?type=entry

Regards,

Puloma.

[Former Member · Accepted solution]

ping xiprd is ok, and response time is 2ms.

and the url result in the browser is :

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header />

- <SOAP:Body>

- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<faultcode>SOAP:Client</faultcode>

<faultstring>Empty HTTP request received</faultstring>

<faultactor>http://sap.com/xi/XI/Message/30</faultactor>

- <detail>

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

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>

</SAP:Error>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

I think nothing goes bad.

[Former Member · Accepted solution]

Hi Bu,

Does SLDCHECK from Sender SAP system work?

Also, in SM59, test connections of type TCP/IP, as well as HTTP Conncections to R3 system.

Use fully-qualified hostnames everywhere.

Regards,

Puloma.

[Former Member · Accepted solution]

we use two system to make a load-balance on ECCPRD, but we miss configuration the XIPRD hostname on the second system. So when load-balance took place, the message on the second system can not send to XIPRD and it gave the message backto the first system. Then the first system sent the message to the XIPRD finally.

Thanks for your help.

B'rgdz.

Alex

[Former Member · Accepted solution]

Hi,

This is a common source of error in load-balanced systems. Make sure that all entries in SMICM are always correct in bother servers.

Regards,

Puloma.

[Former Member]

Hi, bu ju

Take a look at note 824554 and try to enlarge icm/conn_timeout.

[prateek]

Hi,

Refer these weblogs

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Also refer to this

Regards,

Prateek