Skip to Content
Aug 17, 2005 at 07:13 AM




I have set up the following scenariro:

Synchronous Communication between SAP R/3 and an external Orcale Database via ABAP-Proxy on the R/3-Side and JDBC on the Oracle-Side. The whole thing works fine as long as the requests don't get too big.

But now I have to make an initial Download from the Oracle-DB which approximately lasts about 5 hours. In this case my "Timeout-Problem" begins:

In R/3 I get the following Error in SXMB_MONI:

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

- <!-- Eingangs-Message



<SAP:Context />


<SAP:Text language="DE">Fehler beim Empfangen per HTTP (Fehlercode: 402, Fehlertext: ICM_HTTP_TIMEOUT)</SAP:Text>


In XI the following Erorr appears:

-" xmlns:SOAP="" SOAP:mustUnderstand="1">





<SAP:P3 />

<SAP:P4 />

SAP Web Application Server Help" target="_blank">">Help SAP  

500 Connection timed out

Connection timed out (-5)

Error: -5 Version: 6040 Component: ICM Date/Time: Wed Aug 17 02:21:14 2005 Module: icxxthr_mt.c Line: 2559 Server: cat01135_XY1_01 Detail: Connection to partner timed out

©" target="_blank">">©; 2001-2003, SAP AG

<SAP:ApplicationFaultMessage namespace="" />

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



The trace in R/3 doesn't say anything important I think.

The trace in XI is only a little more interesting:

- <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">

<Trace level="3" type="T">Channel for adapter engine: JDBC</Trace>

<Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP" />

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


<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET): af.xy1.cat01135</Trace>

<Trace level="3" type="T">URL = http://cat01135:50100/MessagingSystem/receive/AFW/XI</Trace>

<Trace level="3" type="T">User = XIISUSER</Trace>

<Trace level="3" type="T">Cached =</Trace>

<Trace level="3" type="T">Creating HTTP-client</Trace>

<Trace level="3" type="T">HTTP-client: creation finished</Trace>

<Trace level="3" type="T">Security: Basic authentication</Trace>

<Trace level="3" type="T">Serializing message object...</Trace>

<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 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 level="1" type="T">SystemError message generated. Guid: 43010F97F29A007F020000000A180A87</Trace>

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

<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 43010594DCA300A0020000000A180A28</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>


Has anybody an idea, which Parameter(s) can be responsible for this situation ???

I tried to lift up the TIMEOUT-PARAMETERS on both sides. Here are the Parameters in R/3:

icm/server_port_0 PROT=HTTP,PORT=1080,TIMEOUT=36000

icm/keep_alive_timeout (sec.) = 60

icm/conn_timeout (msec.) = 5000

Here are the Parameters in XI:

icm/server_port_0 = PROT=HTTP,PORT=8001,TIMEOUT=34200

icm/keep_alive_timeout (sec.) = 60

icm/conn_timeout (msec.) = 5000

The Timeout always comes after 15 min.

Would be great if anybody has an idea - Thanks a lot

Werner Knapp