Configure error logging for internal Web server HTTP transport
In order to debug potential problems with using HTTP transport as an internal Web server, you may use the following error logging capabilities.
- To turn error logging on, add the following property to the transport section of the server.xml file and set the value to false...
Property name: ErrorLogDisable Value: True/False Default: Error log is disabled by default Scope: Virtual/Global- To specify your own error log file, add the following property to the transport section of the server.xml file
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"/>Property name: ErrorLog Value: <filename> Default: logs/<server instance>/http.logNote that The error log should appear in each instance of the server.
- Add the LogLevel property to the transport section of the server.xml file to specify the level of messages to log in error log file
Log levels specify what type of message appears in the error log. The warn, error, and crit messages are logged by default.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- To disable error logging, add the ErrorLogDisable property to the transport section of the server.xml file and set the value to true...
Property name: ErrorLogDisable Value: True/False Default: Error log is disabled by default Scope: Virtual/Global- Restart the server.
If you have enabled error logging and encounter an error, there should be an error log message in the error log file you specified.
See Also
Configuring transports
Configuring access logging for internal Web server HTTP transport