Set log levels - Set log levels - Alfresco - Alfresco Content Services - Alfresco/Alfresco-Content-Services/23.4/Alfresco-Content-Services/Administer/Troubleshooting/Set-log-levels - 23.4 - 23.4

Alfresco Content Services
Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License
ft:lastPublication
2026-04-22T22:35:19.567073
ft:locale
en-US

The log4j2.properties file lets you configure logging levels to provide debugging information when troubleshooting. You can set the log level dynamically using the JMX client.

When using log4j, you should:

  • Keep local customizations and licenses outside of the web application. For example, in the extension directory:

      $TOMCAT_HOME/shared/classes/alfresco/extension/...-log4j2.properties

  • The supplied configuration files should be stored or installed within the web application. For example:

      WEB-INF/classes/alfresco/extension/...-log4j2.properties
Note: A dev-log4j2.properties file should not be packaged as a part of any product.

Logging uses the Log4J LoggerContextAdminMBean.

Note: Log levels are not cluster-aware. If needed, the log level change will need to be applied to each machine. Some consoles (for example, JManage) can provide basic facilities for accessing each machine in an application cluster.

  • The Loggers component of the LoggerContextAdminMBean is a dynamic list of loggers with the level attribute, which can be changed to OFF, FATAL, ERROR, WARN, INFO, DEBUG or TRACE (editable).

  • addLoggerMBean will be impacted if it has been loaded.

    The following steps provide instructions on adding loggers using JConsole:

  1. Click Alfresco > Log4jManagement > Operations > addLoggerMBean.

  2. Type the full className in Name on the right hand pane.

  3. Click addLoggerMBean.

    A dialog box is displayed specifying that the method is successfully invoked.