A server can have both active and passive routes. That is, you can configure server S to initiate routes, and also configure other servers to initiate routes to S.
You can specify and modify the properties of an active route, but not those of a passive route. That is, properties of routes are associated with the server where the route is configured, and which initiates the connection.
Two servers can both configure an active route one to the other. This arrangement is called an
active-active configuration. For example, server A specifies a route to server B, and B specifies a route to A. Either server can attempt to initiate the connection. This configuration results in only one connection; it does
not result in redundant routes.
You can promote an active-passive route to an
active-active route. To promote a route, use this command on the passive server:
The url argument is required, so that the server (where the route is being promoted) can connect to the other server if the route becomes disconnected. See also
create route on page 126.
The promoted route behaves as a statically configured route—that is, it persists messages for durable subscribers, and stores its configuration in
routes.conf, and administrators can modify its properties.