Understanding the logger hierarchy

WebSphere Application Server handlers are attached to the Java root logger in the logger hierarchy. As a result, any request from anywhere in the logger tree can be processed by WAS handlers. WebSphere Application One can configure the system to do the following tasks:

• Forward all application logging requests to the WebSphere Application Server handlers. This is the default behavior.

• Forward all application logging requests to your own custom handlers. To do this, set useParentHandlers to false on one of your custom loggers, and then attach your handlers to that logger.

• Forward all application logging requests to both WebSphere Application Server handlers, and your custom handlers, but do not forward WebSphere Application Server logging requests to your custom handlers. To do this, set useParentHandlers to true on one of your non-root custom loggers (true is the default setting) , and then attach your handlers to that logger.

• Forward all WAS logging requests to both WAS handlers, and your custom handlers. WebSphere Application Server logging requests are always forwarded to WebSphere Application Server handlers. To forward WAS requests to your custom handlers, attach your custom handlers to the Java root logger, so that they are at the same level in the hierarchy as the WebSphere Application Server handlers.

The example below shows how these requirements can be met using the Java logging infrastructure.

 

---