Configure error logging for internal Web server HTTP transport

 

+

Search Tips   |   Advanced Search

 

Overview

To debug potential problems with using the HTTP transport as an internal Web server, use the following error logging capabilities.

 

Procedure

  1. Turn error logging on. To turn error logging on, add the following custom property to the HTTP Transport's configuration settings, and set the value to false 

    Property name: ErrorLogDisable 
Value: True/False
Default: Error log is disabled by default

    When you are ready to turn error logging off, set the value of the ErrorLogDisable property back to true.

  2. To specify your own error log file, add the following property to the transport section of the server.xml file: 

    Property name: ErrorLog
Value: <filename>
Default: logs/<server instance>/http.log

    The error log property is used to specify where to place the error log. For example:

    <properties xmi:id="WebContainer_Property_6" name="ErrorLog" value="logs/<server instance>/http.log"/>

    Note: The error log should appear in each instance of the server.

    If you are going to be using error logging for multiple HTTP transports in a single HTTP server, make sure you specify a unique filename for the error log file associated with each HTTP transport.

  3. Add the LogLevel property to the transport section of the server.xml file to specify the level of messages to log in the error log file. 

    Property name: LogLevel
Value:  <level> (Levels include: debug, info, warn, error, crit)
Default:  warn (warn includes error and crit; debug includes all levels)
Scope:  Virtual/Global

    Log levels specify the type of message that appears in the error log. The warn, error, and crit messages are logged by default.

  4. Restart the server.

 

Result

If you have enabled error logging and encounter an error, there should be an error log message in the error log file you specified.

 

Related Tasks


Configure access logging for internal Web server HTTP transport