If you are unable to resolve technical problems, this topic describes log files, and the process for gathering log files and sending them to your IBM® services representative.
The following table lists the available log levels and their meanings.
Log level | Description |
---|---|
OFF | No events are logged. |
FATAL | Task cannot continue and component cannot function. |
ERROR | Task cannot continue, but component can still function. |
WARN | Potential error or impending error. |
INFO | General information outlining overall task progress. |
CONFIG | Configuration change or status. |
DETAIL | General information detailing subtask progress. |
FINE | Trace information - general trace + method entry / exit / return values. |
FINER | Trace information - detailed trace. |
FINEST | Trace information - a more detailed trace that includes all the detail that is needed to debug problems. |
ALL | All events are logged. Can provide a more detailed trace than FINEST. |
A message is logged if the logging request's priority is greater than or equal to the currently assigned priority of the utilized logger. For example, if you have a logger with an assigned log level of INFO, then an ERROR request will pass the approval, but a DETAIL request will be blocked. Level ALL causes a logger to accept all logging request; OFF blocks all requests.
Follow these steps for configuring logging:
Log files are stored in the WAS_HOME\profiles\profile_name\logs directory.
Turning off logging
For more information on how to configure logging, consult the log4j-documentation available at: http://logging.apache.org/log4j/docs/documentation.html
Additional logs are found in the WAS_PROFILE_HOME\logs\server1directory.