ICM_HTTP_TIMEOUT 402 error - ABAP client proxies

[Former Member]

We are using ABAP client proxies to send data from SAP to XI in synchronous scenario.

We did follow the weblog /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies and activated proxies.

Able to generate proxy classes in SAP sender system and wrote ABAP report to trigger proxies (call proxy class).

While executing ABAP report in SAP Sender system, in SXMB_MONI we are getting following error:

<a href="http://help.sap.com/">Help </font></td><td width=5% nowrap></font></td> </tr></table> </td><td rowspan=2 width=122 height=61 valign=top>!http://xihost:50080/sap/public/icman/img/theme.jpg|alt=SAP|width=122 height=61 border=0 |src=http://xihost:50080/sap/public/icman/img/theme.jpg!</td> </tr><tr><td background="http://xihost:50080/sap/public/icman/img/graybar_tile.jpg" height="31">  </td></tr> </table> <br><br> <table width=800> <tr><td width=50 nowrap> </td><td> <H2>500 Connection timed out</H2><br>Connection timed out (-5) <br><hr> <table border="0"> <tr><td>Error:</td><td>-5</td></tr> <tr><td>Version:</td><td>6040</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Tue Jan 30 15:58:35 2007 </td></tr> <tr><td>Module:</td><td>icxxthr.c</td></tr> <tr><td>Line:</td><td>2553</td></tr> <tr><td>Server:</td><td>SAPHOST_ECD_00</td></tr> <tr><td>Detail:</td><td><b>Connection to partner timed out</b></td></tr> </table> <p></p> </td></tr></table> <table><tr><td width=50 nowrap></td> <td nowrap><FONT SIZE=-1><a href="http://www.sap.com/">© 2001-2003, SAP AG</a>.

Thank you for your time looking at this question and problem.

Thanx&Regards

Navin

[agasthuri_doss]

Hi,

1)ST22 check out any Dump.

2) In RWB .. Component Monotring..check the Cache connectivity test...is all are Green ( Glowing )

Regards

Agasthuri Doss

[agasthuri_doss]

Hi,

Error Messageà HTTP 500 - Internal Server Error (an Internal server error)

Solution:

Access the trace file and search for traces with severity ERROR, WARNING or stack traces.

If we do not find an error in the log file or the error message does not explain the problem sufficiently, access the default Trace. The default trace file contains detailed messages for developers. Extract the relevant trace information e.g. using the time stamp or the message ID.

If this does not explain the problem in more detail, increase the trace level and reproduce the problem. Then restart message processing using the message display tool. Mark the message and select repeat.

Regards

Agasthuri Doss