on 11-02-2012 9:29 AM
Hi Experts,
Some of the synchronous transactions getting "500 Internal Server Error" , the scenario is LEGACY SYSTEM->SOAP->PI->PROXY->ECC, Please help to resolve this issue.
"HTML Error"
Error: | -1 |
Version: | 7200 |
Component: | ICM |
Date/Time: | Fri Nov 02 14:09:49 2012 |
Module: | icxxthrio.c |
Line: | 1957 |
Server: | XXXXXXXXXXXXXXXXXXXX - This is ECC Server |
Error Tag: | {0006d2d3} |
Detail: | IcmHandleNetWrite(id=6/53971): No data from server received (rc = -1) |
"Call Adapter Error"
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Adapter
-->
</SAP:Error>
"Error Trace"
<Trace level="1" type="T">Addressing mode: destination</Trace>
<Trace level="1" type="T">Destination = PIPROD_TO_ECC</Trace>
<Trace level="1" type="T">Serializing message object...</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 6394</Trace>
<Trace level="1" type="T">Timeout: 300</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>
Please do the following....
a) Check in SXMB_MONI in PI to see what steps the message fails. I think your error message shows the problem at the call adapter stage. Is that right? The problem seems at ecc side not in pi.
b) Go to ECC and check your proxy implementation logic. This could be anything some validation failed or null data at the proxy processing logic area or some dump error.
c) I would do this. Take help from abap application developers and do the proxy testing withing ecc itself using the same data that failed in PI. This would give lot of insight about this error.
Best of luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>The problem is some messages are getting pass and some fail, the fails are getting "internal server error".
That means this should be values that fails due to validation against backend logic for some messages and not for all. Please check the field values you pass to ECC and work with abaper to find out the exact processing logic error.
Hi Baskar,
BASKAR RAMASAMY wrote:
<SAP:Stack>Error while sending by HTTP (error code: 500 , error text: Internal Server Error) (See attachment HTMLError for details)</SAP:Stack>
You'll find this HTML attachment when you open the message in error on PI (SXMB_MONI). Does this HTML attachment contain more detail on the error you could share with us?
Regards, Trevor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.