cancel
Showing results for 
Search instead for 
Did you mean: 

Error in Soap to Proxy interface

svalluri23
Participant
0 Kudos

Hi Experts,

In Production client, getting the error in sxmb_moni is

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

- <!-- Call Adapter

-->

- <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_SEND_FAILED</SAP:Code>

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

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

<SAP:P3>(See attachment HTMLError for details)</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while sending by HTTP (error code: 500, error text: Timeout) (See attachment HTMLError for details)</SAP:Stack>

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

</SAP:Error>

HPML error is

SAP NetWeaver Application Server Help

500 Connection timed out

-

-


Error: -5

Version: 7000

Component: ICM

Date/Time: Thu Jul 7 14:34:35 2011

Module: icxxthr_mt.c

Line: 2707

Server: ciSP6_SP6_00

Error Tag: {-}

Detail: Connection to partner timed out after 3000s

© 2001-2009, SAP AG

in Communication Channel monitoring getting

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 2a05edb0-a870-11e0-8527-001cc4fb5cb7(OUTBOUND) expired.

How to resolve this issue. Production Server also has been restarted but same error coming. please guide me for further. ICM time also has been increased.

Regards,

Accepted Solutions (0)

Answers (5)

Answers (5)

abhay_rajhans2
Contributor
0 Kudos

Hi,

Please check if the target system up and running.

If you are using ABAP proxy at receiver end, then check the SM59 connection which you are using in the XI adapter.

former_member472138
Active Contributor
0 Kudos

Hello,

Ensure that connection is fine between PI and ECC.

Use xml SPY for triggering message and use in receiver XI adapter authetication(no ananymous) - provide credentials.

Also I would see HTTP 500 is

o Internal error in Java.

o Check the default trace file of the Java Engine using the SAP NetWeaver Administrator.

Regards

Pothana

Former Member
0 Kudos

Hi Hari,

Since your message is reached from SOAP sender to PI (You are able to see your Message Payload in SXMB_MONI) you must concentrate on you connection between PI to Proxy (ERP) Server. I guess you are doing ABAP Server Proxy. For which check the connection RFC Destination of type H pointing from PI to ERP. Check the port is open for ERP connection from PI with in the RFC destination (Service Number). Once it is open, you can execute your Interface without any issues.

Regards

Praveen K

samiullah_qureshi
Active Contributor
0 Kudos

As Praveen describe, u should concentrate on the connection between SAP PI and Proxy(ERP). If you have already configured all required configuration then check the message in SXI_MONITOR of ECC. You will find the your message there if it is at all reached there.

If you find your message there in ECC, then you have to check your inbound proxy code. In that case please test your proxy from SPROXY using the same payload sent by PI.

former_member463616
Contributor
0 Kudos

Hi,

Please refer the following thread:

GabrielSagaya
Active Contributor
0 Kudos

Please check this blog

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

Also Refer the sap note: 824554

Thanks

Gabriel