Chapter 1. Enhancements

This section describes a highlighted set of enhancements and new features in AMQ Broker 7.9. For a complete list of enhancements in the release, see AMQ Broker 7.9.0 Enhancements.

Note

If you require the latest AMQ Broker Long Term Support (LTS) release version, see AMQ Broker 7.8.

AMQP server connections
A broker can initiate connections to other endpoints using the AMQP protocol. This means, for example, that the broker can connect to other AMQP servers and create elements on those connections. This feature is implemented using the <broker-connection> element as described in Configuring AMQ Broker.
Operator supports watching all or multiple namespaces

In previous releases, you installed the AMQ Broker Operator in every namespace you required a broker deployment. Starting in 7.9, the AMQ Broker Operator supports watching all or multiple namespaces for broker custom resources. For more information, see Deploying AMQ Broker for On-Premise.

Note

If you have already installed a previous version of the AMQ Broker Operator in a namespace on your cluster, Red Hat recommends that you do not install the AMQ Broker Operator 7.9 version to watch that namespace to avoid potential conflicts.

Temporary queue namespace
In AMQ Broker 7.9, you can specify a temporary-queue-namespace in the broker.xml configuration file. You can then specify address settings that match the namespace and the broker applies those settings to all temporary queues. If a temporary queue namespace does not exist, temporary queues use the same address settings configuration as other queues. For more information, see Applying specific address settings to temporary queues in Configuring AMQ Broker.
Operator channels

The AMQ Broker Operator Red Hat Integration - AMQ Broker for RHEL 8 (Multiarch) is available with the following channels:

  • 7.x - This channel will install 7.9 and update to 7.10 when available.
  • 7.8.x - This is the Long Term Support (LTS) channel.

To determine which Operator to choose, see the Red Hat Enterprise Linux Container Compatibility Matrix.

Hosts verified by default
The default value for verifyHost has changed from false to true when applied to connectors. All inter-broker connections now verify hosts by default. The default value for acceptors continues to be false.
Enabling the Prometheus plugin using a CR
You can enable the Prometheus plugin on OpenShift using a CR in addition to enabling the plugin using an environment variable. Both options are described in Deploying AMQ Broker for On-Premise.