. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 17.2. Build your own Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transports that can be found here. The default configuration shipped with the ActiveMQ Artemis distribution comes with a number of acceptors already defined, one for each of the above protocols plus a to a newer version. • 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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 17.2. Build your own Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transports that can be found here. The default configuration shipped with the ActiveMQ Artemis distribution comes with a number of acceptors already defined, one for each of the above protocols plus a to a newer version. • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.14.2. Upgrading from 2.26.0 Client applications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 17.2. Build your own Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transports that can be found here. The default configuration shipped with the ActiveMQ Artemis distribution comes with a number of acceptors already defined, one for each of the above protocols plus a to a newer version. • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.13.2. Upgrading from 2.26.0 Client applications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 17.2. Build your own Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transports that can be found here. The default configuration shipped with the ActiveMQ Artemis distribution comes with a number of acceptors already defined, one for each of the above protocols plus a to a newer version. • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.12.2. Upgrading from 2.26.0 Client applications

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 17.2. Build your own Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . transports that can be found here. The default configuration shipped with the ActiveMQ Artemis distribution comes with a number of acceptors already defined, one for each of the above protocols plus a to a newer version. • The client and broker now use SLF4J for their logging API. • The broker distribution now uses Log4J 2 as its logging implementation. 15.11.2. Upgrading from 2.26.0 Client applications

ActiveMQ distribution has been extracted to as ${ARTEMIS_HOME} directory. Installation After downloading the distribution, the following highlights some important folders on the distribution: broker's classpath. This can be done by placing the jar file in the lib directory of the broker distribution itself or in the lib directory of the broker instance. A broker instance does not have a lib /bin/activemq run . The ActiveMQ Artemis broker follows a different paradigm where the project distribution serves as the broker "home" and one or more broker "instances" are created which reference the

ActiveMQ distribution has been extracted to as ${ARTEMIS_HOME} directory. Installation After downloading the distribution, the following highlights some important folders on the distribution: ones, the run scripts are the place to do it. Using the Server 22 Pre-configured Options The distribution contains several standard configuration sets for running: Non clustered stand-alone. Clustered simple as that. For a wide range of working JMS examples please see the examples directory in the distribution. Warning Please note that JMS connections, sessions, producers and consumers are designed to

ActiveMQ distribution has been extracted to as ${ARTEMIS_HOME} directory. Installation After downloading the distribution, the following highlights some important folders on the distribution: tune the existing ones, the run scripts are the place to do it. Pre-configured Options The distribution contains several standard configuration sets for running: Non clustered stand-alone. Clustered simple as that. For a wide range of working JMS examples please see the examples directory in the distribution. Using JMS 59 Warning Please note that JMS connections, sessions, producers and consumers

instance to a newer 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 client 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 should stop using the module as it will not be maintained any more. 3. We removed web content from distribution and redirected to the console web requests with the root target as part of ARTEMIS-3980. If you

instance to a newer 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 client 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 stop using the module as it will not be maintained any more. 3. We removed web content from distribution and redirected to the console web requests with the root target as part of ARTEMIS-3980. To enable