Skip to Content
avatar image
Former Member

Received HTTP response code 500 : Internal Server Error.

Hi All

I am running a BPM Scenario in my XI instance. It was running fine without any issues. Recently we have noticed that step 1 of the BPM gets triggered ( Triggered on arrival of a file ). But the BPM has such doesnot trigger.

We have checked Cache. BPM Process Engine settings and status and Queue Monitors etc. Everthing seems to be fine.

The Error as reported in Message Monitoring is as follows

Transmitting the message to endpoint http://saptst01.com:8010/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Internal Server Error.

2006-10-10 01:40:17 Success The asynchronous message was successfully scheduled to be delivered at Tue Oct 10 01:45:17 GMT-07:00 2006.

2006-10-10 01:40:17 Success The message status set to WAIT.

2006-10-10 01:45:17 Success Retrying to send message. Retry: 1

2006-10-10 01:45:17 Success The message was successfully retrieved from the send queue.

2006-10-10 01:45:17 Success The message status set to DLNG.

2006-10-10 01:45:17 Error Transmitting the message to endpoint http://saptst01.com:8010/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Internal Server Error.

This is retried three times and then is is marked to status NDLV.

Any thoughts on what could be the potential issue ??

Regards

Aju Paul

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Oct 11, 2006 at 06:14 PM

    Hi,

    The state assigned to a message when an administrator decides to abort sending the message, or when a message could not be delivered due to a fatal exception that cannot be repaired.

    Error Messageà HTTP 500 - Internal Server Error (an Internal server error)

    Solution:

    Access the trace file and search for traces with severity ERROR, WARNING or stack traces.

    If we do not find an error in the log file or the error message does not explain the problem sufficiently, access the default Trace. The default trace file contains detailed messages for developers. Extract the relevant trace information e.g. using the time stamp or the message ID.

    If this does not explain the problem in more detail, increase the trace level and reproduce the problem. Then restart message processing using the message display tool. Mark the message and select repeat.

    Regards

    Agasthuri Doss

    Add comment
    10|10000 characters needed characters exceeded