Show TOC

Monitoring Internal Server Error 500 Error ResponsesLocate this document in the navigation structure

Use

According to the HTTP specification, 500 "Internal Server Error" occurs when the server encounters an unexpected condition which prevents it from fulfilling the HTTP request. There are two available monitors whose purpose is to provide consistent and up-to-date overall statistics about the 500 "Internal Server Error" error responses. These monitors also enable you to keep track of the most common problems and be aware of the current status of the system according to the green/yellow/red light of the monitors. The tasks of both monitors are interrelated:

  • Error500Count counts the number of all Internal Server Error 500 errors gathered for 24 hours. When this period expires, the count is reset.

  • Error500CategorizationEntries keeps detailed statistics about all 500 "Internal Server Error" error responses. The collected information is sorted per categorization ID, which is a unique identifier of each particular problem that has caused 500 "Internal Server Error" . The information is displayed in descending order, starting with the most common problem. You can also use the categorization ID to search for a particular problem in the trace files.

Procedure

Using 500 Internal Server Error-Related Monitors

  1. In the SAP NetWeaver Administrator, choose Start of the navigation path Availability and Performance Management Next navigation step Resource Monitoring Next navigation step Java System Reports End of the navigation path.

  2. From the Report dropdown list, select Monitor Browser .

  3. Expand the nodes of the Monitoring Tree : Start of the navigation path Server Next navigation step Services Next navigation step Web Container End of the navigation path.

  4. To display the number of the Internal Server Error 500 errors gathered for the last 24 hours, select the Error500Count monitor. You can also check the time of the last reported error response.

  5. To display the different categories of the generated errors, select the Error500CategorizationEntries monitor. Select the Current Values tab in the Details section. There you can find information about the categorization ID of error responses, how many times it has occurred, and a list of the previously generated error reports related to this problem, if any.

More information: Managing Monitors with the Monitor Browser

Note

To specify the time interval in seconds at which the 500 Internal Server Error -related monitors are regularly cleared, change the value of the Error500MonitorsCleanupPeriod property:

  1. Open the SAP NetWeaver Administrator.

  2. Choose Start of the navigation path Configuration Management Next navigation step Infrastructure Next navigation step Java System Properties End of the navigation path. Specify a template in the Templates section.

  3. Choose the Services tab in the Details section.

  4. Choose the Web Container service.

  5. Select the Error500MonitorsCleanupPeriod property in the Extended Details section. Choose Modify .

  6. Enter the new value of the property. Choose Set and then Save .

Note

To clean the values of both monitors in one go without changing their configuration, use the following Telnet command:

               >add servlet_jsp

               >clear_error500_monitors

Accessing 500 Internal Server Error-Related Log Files

  1. In the SAP NetWeaver Administrator, choose Start of the navigation path Problem Management Next navigation step Logs and Traces Next navigation step Log Viewer End of the navigation path.

  2. From the Customization dropdown list, select Perspectives . Select the HTTP checkbox and choose OK .

  3. From the Show View dropdown list, select Start of the navigation path Predefined Next navigation step HTTP Next navigation step Error 500 End of the navigation path.

A detailed list of all 500 Internal Server Error -related log files appears. It contains information about the severity of the log files, the exact time and date when the error occurred, a description of the error, its location and category, and the application that itis related to.