EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB16162: How to enable IBM WebSphere Application Server HTTP error log


Community Admin

• Strategy


How to enable IBM WebSphere Application Server HTTP error log

The IBM WebSphere Application Server HTTP error log allows administrators to capture error logs at different levels (e.g. critical, error, warning, information, and debug). To enable the IBM WebSphere Application Server error log for troubleshooting purposes, follow the steps below:
 

  • Navigate to Servers > Application Servers > server1 > Web Container Settings > Web Container Transport Chains > HTTP Inbound Channel > HTTP error and NCSA access logging.

    Tip: A shortcut is Servers > Application Servers > server1 > HTTP error and NCSA access logging.

     
  • Check 'Enable service at server startup' and 'Enable error logging' as shown below:
ka04W000000Og1yQAC_0EM4400000028mO.jpeg
  • Set the location of the log file. By default, the error logs will be saved in ${SERVER_LOG_ROOT}/http_error.log.
  • Specify the logs maximum size.
  • Specify the error level:
     
    • Critical: Logs only errors that stop WebSphere Application Server from functioning properly.
    • Error: Logs errors that deal with responses to clients that are logged. If the error is caused by server configurations settings, it will require intervention from the WebSphee Application Server.
    • Warning: Logs general errors (e.g. socket exceptions).
    • Information: Logs status of various tasks performed while handling requests.
    • Debug: Logs verbose task status. Warning: This level requires a large log file size and may impact performance.
  • Apply the changes.
  • Save the changes to the master repository.
  • Restart IBM WebSphere Application Server for the changes to take place.

Comment

0 comments

Details

Knowledge Article

Published:

July 13, 2017

Last Updated:

July 13, 2017