HTTP_RESP_STATUS_CODE_NOT_OK -- 500 -- Timeout

[Former Member]

Hi Guys,

There is 1 msg gone to error status with below error .

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

- <!-- Call Integration Server

-->

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

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

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

<SAP:P1>500</SAP:P1>

<SAP:P2>Timeout</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error when sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>

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

</SAP:Error>

This error happened only once and again all the msgs for the same interface processing successfully.

Scenario is: proxy --> XI --> IDoc(Asynchronous)

Could any one plz let me know wht could be the problem that time?

Thanx,

Kumar

[Former Member]

Hi Kumar,

as far as I understood your problem, the Timeout error occurs when sending from

ABAP Proxy (?) to the Integratin Server, correct?

Please check with transaction SMICM on both sides the trace file and the parameter settings for the http protocol.

It could be that your message is quite large, and therefore the default values of 60 seconds are to small defined.

In general for Timeout settings, there is a nice unit called "Timeouts in XI" in the XI3.0/XI7.0 Troubleshooting Guide available at

<a href="http://service.sap.com/instguidesNW70">http://service.sap.com/instguidesNW70</a> > Operations

- Process Integration: <a href="http://Troubleshooting Guide - SAP XI 3.0/SAP NW 7.0">http://service.sap.com/~sapidb/011000358700005909032005E.PDF</a>

Extract from the guide, which should be also valid for your case:

ICM 402 timeout for http client calls (IS -> AF): ICM_HTTP_TIMEOUT

Value for all ports: icm/keep_alive_timeout (Default: 60 seconds)

Value for specific ports:

icm/server_port_0 = PROT=HTTP,PORT=<icmhttpport>, TIMEOUT=30, PROCTIMEOUT=900

PROCTIMEOUT not set > TIMEOUT is used > TIMEOUT not set > icm/keep_alive_timeout is used

Default: TIMEOUT and PROCTIMEOUT not set –>icm/keep_alive_timeout is used

In the event of errors, increase the PROCTIMEOUT value for the HTTP/HTTPS ports used.

Do not increase icm/keep_alive_timeout or the TIMEOUT value as this would lead to a higher resource consumption.

For more information, see SAP Note 824554 - ICM timeout parameters.

Best regards,

Silvia

[Former Member]

Hi,

Http Errors in XI

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

vasanth

[Former Member]

Hi,

There can be many cause of these problem. Some of the servers can be overloaded or message is big.

You can schedule these program to automatically restart messages with error status: SXMB_RESTART_MESSAGES

You can also increase http timeout in sxmb_adm

best,

Wojciech

[former_member201264]

hi

i also had the same problem.

this is bcoz of the system load, whenever there is over load on the server in will give this error, it will settle down after some time or u can restart the msg again.

regards

sreeni

[Former Member]

Hi,

Thanks for ur reply.

I restarted the msg imediately after I saw the error. That is not the problem.

Is it psb to see any log that system overloaded that time becoz customer asking the reason of failure with proof.

Thanx,

Kumar

[Former Member]

Hi,

I recommend to use transaction STUN. There can be many reasons.

check Michal's blog

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

/wg