JMX Management - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

Configuring loggers at runtime via JMX

The Alfresco:Name=Log4jHierarchy JMX bean has now been replaced by Alfresco:Name=Log4jManagement. This new implementation does not expose APIs to change the logger thresholds at runtime since it is unnecessary.

The very same operation should now be performed instead via the native Log4j 2.x org.apache.logging.log4j2:type=<LogContextName>,component=Loggers beans instead (note that the <LogContextName> is not a fixed value).

The Loggers component contains a dynamic list of beans that allow the reconfiguration of loggers at runtime by editing their attributes:

Attribute name Example value
Level WARN
Additive true