. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 16.1. General Upgrade Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with then the steps from each version need to be followed in order.  Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions

then the steps from each version need to be followed in order. Note: Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions as outlined above, you can instead perform the update manually, following the general upgrading procedure plus the additional steps below: 1. The new /etc/log4j2.properties file should be created providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with

then the steps from each version need to be followed in order. Note: Follow the general upgrade procedure outlined in the Upgrading the Broker chapter in addition to any version-specific upgrade instructions outlined above, you can instead perform the update manually, following the general upgrading procedure plus the additional steps below: 1. The new /etc/log4j2.properties file should be created providing reliability, transactions and many other features. Unlike systems based on a Remote Procedure Call (RPC) pattern, messaging systems primarily use an asynchronous message passing pattern with