Previous Topic: Additional Storage Management Interface Administrator TasksNext Topic: How to Change the Log Level Temporarily


Managing CA Chorus Logs

How to Change the Log Threshold for All Executions

As a system administrator, you can edit the log level or threshold without restarting the JBoss server. Doing so changes the log level for all executions.

Note: All log files are located in /cai/cetjr3m0/logs by default.

Add the following JBoss property to the ENVETJ member of chorus_runtime_hlq.CETJOPTN (before the lines to Export all Java SDK options):

jboss.server.log.threshold

Specifies the log level or threshold on a running JBoss server. The log level determines the amount of information that is written to the log files. These log messages appear in the following log files: server.log, server-ebcdic.log, chorus-status.log, and chorus-query.log.

Values: ERROR, WARNING, INFO, DEBUG, and TRACE (in ascending order by amount of detail).

Default: INFO (DEBUG and TRACE categories are not logged).

Important! DEBUG and TRACE log levels can cause high CPU usage and increased disk space usage. Use these values only under the direction of CA support. We recommend that you do not use this property to implement DEBUG or TRACE. In emergency situations, you can enter a command to set the level to DEBUG. See the example in How to Change the Log Level.

Save your changes.

The ENVETJ member is updated and the changes are applied as applicable to the CA Chorus log file.

Example: Change Log Threshold

In this example, the log level is set to DEBUG:

IJO="$IJO -Djboss.server.log.threshold=DEBUG"