Chapter 1. Introduction to AMQ Broker on OpenShift Container Platform
Red Hat AMQ Broker 7.10 is available as a containerized image for use with OpenShift Container Platform (OCP) 4.11, 4.12, 4.13 or 4.14.
AMQ Broker is based on Apache ActiveMQ Artemis. It provides a message broker that is JMS-compliant. After you have set up the initial broker pod, you can quickly deploy duplicates by using OpenShift Container Platform features.
1.1. Version compatibility and support
For details about OpenShift Container Platform image version compatibility, see:
All deployments of AMQ Broker on OpenShift Container Platform now use RHEL 8 based images.
1.2. Unsupported features
Master-slave-based high availability
High availability (HA) achieved by configuring master and slave pairs is not supported. Instead, AMQ Broker uses the HA capabilities provided in OpenShift Container Platform.
External clients cannot use the topology information provided by AMQ Broker
When an AMQ Core Protocol JMS Client or an AMQ JMS Client connects to a broker in an OpenShift Container Platform cluster, the broker can send the client the IP address and port information for each of the other brokers in the cluster, which serves as a failover list for clients if the connection to the current broker is lost.
The IP address provided for each broker is an internal IP address, which is not accessible to clients that are external to the OpenShift Container Platform cluster. To prevent external clients from trying to connect to a broker using an internal IP address, set the following configuration in the URI used by the client to initially connect to a broker.
AMQ Core Protocol JMS Client
AMQ JMS Client
1.3. Document conventions
This document uses the following conventions for the
sudo command, file paths, and replaceable values.
In this document,
sudo is used for any command that requires root privileges. You should always exercise caution when using
sudo, as any changes can affect the entire system.
For more information about using
sudo, see The
About the use of file paths in this document
In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example,
/home/...). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example,
This document sometimes uses replaceable values that you must replace with values specific to your environment. Replaceable values are lowercase, enclosed by angle brackets (
< >), and are styled using italics and
monospace font. Multiple words are separated by underscores (
For example, in the following command, replace
<project_name> with your own project name.
$ oc new-project <project_name>