XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

[Former Member]

I'm getting this message in RWB when trying to send an order:

Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

Weird thing is, other orders have been successfully to the same partner.

Is this something on my side or the receivers side?

What does HTTP 500 Internal Server Error mean and how to fix?

Thanks,

Jeff

[Former Member]

Determined that the partner was receiving the file but their software was preventing it from processing because it did not recognize the schema.

Just wish the error message was a little more helpful; toomk awhile to figure.

Thanks for all teh suggestions.

[Former Member]

More info on this problem:

Discovered that the HTTP 500 error only occurs when a "change" file is sent:

I send an order create file to a partner using a SOAP adapter. They receive it successfully.

I make a change to the sales order and send that file. It uses the same Config Scenario, receiver determination, receiver agreement and comm. Channel.

But this file shows an HTTP 500 error in the RWB.

I send it right after the first order create file, so no overloading is happening, etc.

Conenctivity to the url is fine because the create file went through.

I don't know what else it could be. Any other info/log in RWB to look at to help decipher the error?

[Former Member]

Jeff,

HTTP 500 is always a connectivity issue. please check your Basis folks to find out whether the connectivity between systems are fine.

Regards,

Pavan

[agasthuri_doss]

Jeff,

Sometime this happens when Java engine is overloaded ,

Try this In RWB - Admin Tab

1. Re-initialization (then try logging)

2. Re-initialization and force-signing (then try logging)

Cheers

Agasthuri

[Former Member]

Jeff,

Try to send the same message and test once again. It seems there is some issue in the payload of the response message. Try to open the response message from the success one and the failed ones and compare both. There should be some difference between these two.

Regards,

---Satish

[Former Member]

It is because unexpected state while processing the message.

Have a look @ Note: 804124, 807000

Venkat.