. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 76.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . profile file. • The logging configuration of the CLI commands other than run is configurable via the log4j2- utility.properties file. • The run command has been removed from the artemis shell, use the artemis

version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions Client applications wanting logging application logging for more information plus an example around using Log4J 2. The broker distribution now includes and configures Log4J 2 as its logging implementation, see logging for more details. If changes for the new log4j2.properties file. Versions 9 Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own

version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions Client applications wanting logging application logging for more information plus an example around using Log4J 2. The broker distribution now includes and configures Log4J 2 as its logging implementation, see logging for more details. If changes for the new log4j2.properties file. Versions 10 Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own

version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions Client applications wanting logging application logging for more information plus an example around using Log4J 2. The broker distribution now includes and configures Log4J 2 as its logging implementation, see logging for more details. If analogous changes for the new log4j2.properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration

version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions Client applications wanting logging application logging for more information plus an example around using Log4J 2. The broker distribution now includes and configures Log4J 2 as its logging implementation, see logging for more details. If analogous changes for the new log4j2.properties file. Note also that brokers configuration-file-refresh-period broker.xml setting no longer covers logging configuration refresh. Log4J 2 has its own configuration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 76.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.9.2. Upgrading from 2.26.0 Client applications wanting logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 75.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.7.2. Upgrading from 2.26.0 Client applications wanting logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 75.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.8.2. Upgrading from 2.26.0 Client applications wanting logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 75.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.6.2. Upgrading from 2.26.0 Client applications wanting logging

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 76.2. Request Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . mirroring and paging • Logging metrics to mitigate the risk of missing WARN or ERROR messages in the log. • Much improved documentation on network isolation (aka split brain) • Pluggable lock manager (aka