Skip to Content
0
Sep 03, 2018 at 02:30 PM

Synchronous Soap to Proxy. 500 Connection Timed Out

126 Views Last edit Sep 03, 2018 at 02:38 PM 2 rev

Dear Experts,

I have a Soap (third party) to Proxy (SAP ECC) scenario. The interface was doing just fine. It could take 3-5 minutes to be processed, but never end in error state.

Suddenly, after an upgrade (not really sure what was changed, from the Basis side, they said that they didn't changed anything), the interface always ends up in an error 'HTTP Error: Sending Message'. In the HTML detail it says '500 Connection timed out', but actually in the SXMB_MONI of PI, the Start Time and the End Time interval is only about 30 seconds, while actually it used to takes 3-5 minutes and no timed out error occur.

The questions are: Does the Start Time and the End Time in the SXMB_MONI really reflect the time the message takes for processing? What usually causes 500 Connection timed out at only 30 secs interval? How to investigate this issue further?

Here is a little part message from the trace in the SXMB_MONI:

<Trace type="T" level="1">Serializing message object... </Trace>
<Trace type="T" level="1">HTTP Multipart document length: 8612 </Trace>
<Trace type="T" level="1">Timeout: 0 </Trace>
<Trace type="T" level="1">HTTP-client: request sent</Trace>
<Trace type="T" level="1">HTTP-client: response received</Trace>
<Trace type="T" level="1">HTTP-client: status code = 500</Trace>
<Trace type="T" level="1">Deserializing message object... </Trace>
<Trace type="T" level="1">HTTP-client: parsing failed, status code = 500</Trace>
<Trace type="System_Error" level="1">Error while sending by HTTP (error code: 500 , error text: Internal Server Error) </Trace>

Thank you.

Regards,

Suwandi C.