WAS v8.5 > Troubleshoot > Add logging and tracing to the application > Use Java logging in an application
Configure the logger hierarchy
WebSphere Application Server handlers are attached to the Java root logger, which is at the top of the logger hierarchy. As a result, any request from anywhere in the logger tree can be processed by WAS handlers.
We can configure the application server to handle logs in many different ways. Configure the log settings based upon your configuration and the logging structure that best suits your needs.
- Forward all application logging requests to the WAS handlers. This behavior is the default.
- Forward all application logging requests to our own custom handlers. Set the useParentHandlers option to false on one of your custom loggers, and then attach your handlers to that logger.
- Forward all application logging requests to both WAS handlers,
and your custom handlers, but do not forward WAS logging requests to your custom handlers. Set the useParentHandlers option to true on one of your non-root custom loggers, and then attach your handlers to that logger.True is the default setting.
- Forward all WAS logging requests to both WAS handlers, and your custom handlers. Logging requests are always forwarded to WAS handlers. To forward WAS requests to your custom handlers, attach your custom handlers to the Java root logger, so they are at the same level in the hierarchy as the WAS handlers.
Example
The following example shows how these requirements can be met using the Java logging infrastructure:
Related
Use a logger
Create log resource bundles and message files