MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response code 500 : Internal Server Error

[former_member221434]

Dear Experts ,

Soap to Proxy synchronous scenario is running in PI(7.4) production but some transaction failed due to this error.

Below i have attached screen shot of this error.

Error is :

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

- <!--

 Call Adapter 

--> 

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

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

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

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

<SAP:P2>Internal Server Error</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: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>

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

</SAP:Error>

  Trace:

<Trace level="1" type="T">Addressing mode: destination</Trace>

<Trace level="1" type="T">Destination = ECP_HTTP</Trace>

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

<Trace level="1" type="T">HTTP Multipart document length: 4788</Trace>

<Trace level="1" type="T">HTTP Timeout: SYSTEM("http://sap.com/xi/XI/Message/30/general" "syncTimeout" ) 900</Trace>

<Trace level="1" type="T">Timeout: 900</Trace>

<Trace level="1" type="T">HTTP-client: request sent</Trace>

<Trace level="1" type="T">HTTP-client: response received</Trace>

<Trace level="1" type="T">HTTP-client: status code = 500</Trace>

<Trace level="1" type="T">Deserializing message object...</Trace>

<Trace level="1" type="T">HTTP-client: parsing failed, status code = 500</Trace>

<Trace level="1" type="System_Error">Error while sending by HTTP (error code: 500 , error text: Internal Server Error)</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_TO_PERSIST" />

</Trace>

<Trace level="1" type="T">An Exception has occured</Trace>

<Trace level="1" type="T">Error Text: Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</Trace>

<Trace level="1" type="T">SystemError message generated. Guid:

thanks in advance.

Regards,

Pradeep Kumar.

[manoj_khavatkopp]

HTTP 500 : Internal Error occurs due to many reason  :

The third party server may be down.

The request you are sending is not accepted by the system etc.

As you are saying that only few transaction is being failed then i would suggest you to check with the data which you are sending.

Br,

Manoj

[former_member186851]

Check the points mentioned by Manoj also the connection settings in the proxy channel.

[former_member221434]

Hi Raghu,

I have tested error payload in pi quality it is working fine.

Mostly transactions are executing successfully but every day 20-40 transactions failed, if problem in proxy connection then other transactions should not success.  

Success payload.

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

- <ns0:MT_Mobile_Recharges_Member_Request xmlns:ns0="http://Ad.com">

<Transaction_Request_Number>0083900</Transaction_Request_Number>

<Mobile_Number>7770913578</Mobile_Number>

<Operator>IDEA</Operator>

<Transaction_Amount>19</Transaction_Amount>

<Member_Code>197111</Member_Code>

<NetworkID>+918871141000</NetworkID>

<MAC>mobile</MAC>

</ns0:MT_Mobile_Recharges_Member_Request>

Error Payload .

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

- <ns0:MT_Mobile_Recharges_Member_Request xmlns:ns0="http://Ad.com">

<Transaction_Request_Number>0083090</Transaction_Request_Number>

<Mobile_Number>9200266785</Mobile_Number>

<Operator>INDICOM</Operator>

<Transaction_Amount>120</Transaction_Amount>

<Member_Code>1828789</Member_Code>

<NetworkID>+918889498076</NetworkID>

<MAC>mobile</MAC>

</ns0:MT_Mobile_Recharges_Member_Request>

Regards,

Pradeep Kumar

[former_member186851]

Hello Pradeep,

Some messages are only failing ,I still doubt could be data issue.

Any recent code changes in ABAP Proxy code in Quality not moved to production?

And your getting dump in ST22?

[former_member221434]

Hi Raghu,

Some interface has been running since last one year and some interface new.But this issue has been coming since last 20 days .

BR,

Pradeep

[former_member186851]

Pradeep is this happening in the new ones?

And did you check any changes in code in Quality envi?

[former_member221434]

Hi Raghu,

It's happening both interface.

Error : Received HTTP response code 500 with Body: <html><head><title>Application Server Error</title></head><body>
<H2>500 Connection timed out</H2><br>
<hr>Tue Jul 19 17:54:52 2016

</body></html>
.....................................

SOAP: Call failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Received HTTP response

BR,

Pradeep

[former_member186851]

Hello Pradeep,

Try increasing timeout as per the below link.Before doing it ensure ECC system is up all the time or any issues in ECC.

[former_member221434]

Hi Raghu,

I have increased PROCTIMEOUT 600 to 900 in SMICM But still getting same error.

BR.

Pradeep

[apu_das2]

Try to increase this in ABAP stack SXMB_ADM -> IE Configuration -> Specific Configuration -> maintain HTTP_Time Out here.

Thanks,

Apu

[former_member186851]

Ok Pradeep.

Check the parameter mentioned by Apu.

Check if the ECC system is stable and also for any changes in ECC proxy code.

[former_member221434]

Hi Raghu ,

I have checked failed request message history there found message processing time more than 600 sec and ECC has 600 sec PROCTIMEOUT .

I thought ,May be this is a reason for message fail.

BR,

Pradeep

[apu_das2]

As I said, add the parameter under sxmb_adm.

If require you can add this both in PI and in ECC system.

Thanks,

Apu

[former_member186851]

Might be Pradeep.

Try increasing in SXMB_ADM.

[former_member221434]

Hi Raghu/Apu,

I have increased PROCTIMEOUT(600 to 900) in both system.But now getting different type of error.

Error is :

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

- <!--

 Call Adapter 

--> 

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

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

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

<SAP:P1>402</SAP:P1>

<SAP:P2>Connection to partner timed out after 900s</SAP:P2>

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

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error while receiving by HTTP (error code: 402 , error text: Connection to partner timed out after 900s) (See attachment HTMLError for details)</SAP:Stack>

<SAP:Retry>A</SAP:Retry>

</SAP:Error>

Regards,

Pradeep

[manoj_khavatkopp]

Did u try to execute the proxy directly in ECC with the same data for which you are getting error ?

By trying to increase timeout you are just extending the time to wait for the response.

I would suggest you to test locally in SPROXY of ECC system.

[former_member221434]

Hi Manoj,

it's issue coming in PI Production environment but data or payload tested in quality and its working fine.

BR.

Pradeep 

[former_member186851]

Pradeep I would suggest to raise a OSS note if the issue persists.