#### To Configure Log Levels

1. In the tree component:

   - For the Developer profile, go to Application Server → Logging → Log Levels

   - For the Cluster and Enterprise profiles, go to Configurations → Configuration Name→ Logging → Logging Settings → Log Levels

2. Choose a new value from the drop-down list opposite the module or modules whose log level is to be changed.

   For more information on the modules, see The Logger Namespace Hierarchy.

   Messages at the selected level or higher appear in the log. Choose any of the following values (listed from highest to lowest):

   - `SEVERE`

   - `WARNING`

   - `INFO`

   - `CONFIG`

   - `FINE`

   - `FINER`

   - `FINEST`

   - `OFF`

   The default level is `INFO`, so the log will contain messages of `INFO`, `WARNING`, or `SEVERE` levels.

3. Use the Additional Properties area to configure log levels for any application loggers.

   The property name is the logger namespace, and the value is one of the eight possible levels. For example, the property name could be `samples.logging.simple.servlet`, and the value could be `FINE`.

   Also use this area to change the log level for a submodule, such as the transport submodule of the CORBA module:

       javax.enterprise.resource.corba.ORBId.transport

   Calls to `System.out.println` are logged at the `INFO` level using the logger name `javax.enterprise.system.stream.out`. Calls to `System.err.println` are logged at the `WARNING` level using the logger name `javax.enterprise.system.stream.err`. To turn off the logs from these sources, specify the logger name with the value `OFF` in the Additional Properties area.

4. Click Save to save the changes, or click Default to restore the default values.

   Changes to the Log Level settings take effect immediately. They are also saved in the `domain.xml` file for use when the server restarts.

######

###### More Information

Persistence Log Module

Setting the Persistence module log level will affect JDO and CMP logger settings. The log level shown for Persistence will depend on the value of the property, `oracle.toplink.essentials`.

Use the Add Property button under Additional Module Log Level Properties, to set the logger level for `oracle.toplink.essentials`. You can also use `asadmin set` from the command line: `server.log-service.module-log-levels.property.oracle\.toplink\.essentials"=FINEST`.

If this property is not specified, the value of the Persistence module will be the default, which is INFO.

The log level set for Persistence (through the `oracle.toplink.essentials` property), will be synchronized with JDO, CMP, and the CMP container, only when you set the log value through Admin Console > Logging > Log Levels, and then in the Persistence combo box.

However, if the `oracle.toplink.essentials` property value is set directly, for example, through `asadmin set` command, then toplink's log level alone will be affected. The log level for JDO, CMP, and CMP container will not be affected.

To set log levels for JDO and CMP that are different to that set for Persistence, you need to manually edit the `domain.xml` configuration file. For more information on domain.xml, see Sun Java System Application Server 9.1 Administration Reference

###### See Also

- To Configure General Logging Settings

- The Logger Namespace Hierarchy

- To View the Server Log