Detecting Slow Consumers Avoiding Network Isolation Detecting Broker Issues (Critical Analysis) 2 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 were removed We don't store page counters records on the journal any longer what should simplify operation and improve performance. Upgrading from older versions Due to ARTEMIS-3871 the naming pattern 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 will

Detecting Slow Consumers Avoiding Network Isolation Detecting Broker Issues (Critical Analysis) 2 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 were removed We don't store page counters records on the journal any longer what should simplify operation and improve performance. Upgrading from older versions Due to ARTEMIS-3871 the naming pattern 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 will

Detecting Slow Consumers Avoiding Network Isolation Detecting Broker Issues (Critical Analysis) 2 1.31 1.32 1.33 1.34 1.35 1.36 1.37 1.38 1.39 1.40 1.41 1.42 1.43 1.44 1.45 1.46 1.47 were removed We don't store page counters records on the journal any longer what should simplify operation and improve performance. Upgrading from older versions Due to ARTEMIS-3871 the naming pattern 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 will

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 321 47.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 317 46.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 317 46.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 317 46.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 76.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 331 47.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 331 47.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Why use Apache ActiveMQ Artemis? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Case 2: Target Rate Single producer Single consumer over a queue. . . . . . . . . . . . . . . . . . . . . 329 47.3. Case 3: Target Rate load on 10 durable topics, each with 3 producers and 2 unshared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 77.5. More on Log4J2 configuration: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .