Supported Configurations for Previous Releases of AMQ 7 Broker
Red Hat AMQ broker 7.12
Every Red Hat AMQ broker release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.
AMQ broker 7.12 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 11, 17 |
| OracleJDK | 11,17 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ broker 7.12 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 7 | x86_64 | OpenJDK 11 & 17 , Oracle JDK 11 |
| RHEL 8 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| RHEL 9 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
AMQ broker 7.12 Supported but not Tested Configurations
Red Hat has performed a limited range of platform tests on the following platforms.
| Operating system | Architecture | JVM |
|---|---|---|
| Microsoft Windows Server 2016 | x86_64 | OpenJDK 11 & 17 , Oracle JDK 11 |
| Microsoft Windows Server 2019 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| Microsoft Windows Server 2022 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
Interoperability with FUSE
With regards to FUSE, AMQ broker 7.x is only supported as a remote broker. AMQ Broker 7.x is not certified to run as the internal broker in FUSE 6.x or 7.x. AMQ broker 7.x has been tested and certified to work as an external broker with FUSE 6.x and 7.x components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility | Architecture |
|---|---|---|
| This content is not included.Red Hat AMQ broker 7.12 | OpenShift 4.12,4.13,4.14,4.15,4.16 | x86_64,s390x, & ppc64le |
| This content is not included.Red Hat AMQ broker Operator | OpenShift 4.12,4.13,4.14,4.15,4.16 | x86_64,s390x, & ppc64le |
Note: AMQ 7.8 is the last version of AMQ broker supported on OpenShift 3.11.
Cloud Services
| AMQ broker 7.12 is supported as the following cloud services |
|---|
| Redhat Openshift Service on AWS (ROSA) |
| Microsoft Azure Redhat Openshift |
Note: When running the Broker in AWS it is recommended to use EBS storage instead of EFS. EFS was intended for large storage and not transactional processing and could lead to low throughput which in turn could cause the broker to become unresponsive.
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 and 2019 | v8.4.1 |
| PostgreSQL | 11.5 | v11 |
| Mysql | 8 | v8 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT 5.0 | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | --- | ✅ | ✅ | ✅ | ✅ |
| OpenWire | ✅ | --- | ✅ | ✅ | ✅ |
| CORE | ✅ | ✅ | --- | ✅ | ✅ |
| MQTT 5.0 | ✅ | ✅ | ✅ | --- | ✅ |
| STOMP | ✅ | ✅ | ✅ | ✅ | --- |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7. As AMQ 6 is coming to the end of its life it is strongly recommended that customers that have migrated from AMQ 6 to 7 migrate any remaining OpenWire clients to a modern supported client in one of the other actively supported clients.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 5 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.10 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.12 was built from source using Apache Maven 3.6.3. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.6.3.
Red Hat AMQ broker 7.11
Every Red Hat AMQ broker release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.
AMQ broker 7.11 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 11, 17 |
| OracleJDK | 11,17 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ broker 7.11 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 7 | x86_64 | OpenJDK 11 & 17 , Oracle JDK 11 |
| RHEL 8 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| RHEL 9 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| Microsoft Windows Server 2019 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
Interoperability with FUSE
With regards to FUSE, AMQ broker 7.x is only supported as a remote broker. AMQ Broker 7.x is not certified to run as the internal broker in FUSE 6.x or 7.x. AMQ broker 7.x has been tested and certified to work as an external broker with FUSE 6.x and 7.x components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility | Architecture |
|---|---|---|
| This content is not included.Red Hat AMQ broker 7.11 | OpenShift 4.9,4.10,4.11,4.12,4.13,4.14 | x86_64,s390x, & ppc64le |
| This content is not included.Red Hat AMQ broker Operator | OpenShift 4.9,4.10,4.11,4.12,4.13,4.14 | x86_64,s390x, & ppc64le |
Note: AMQ 7.8 is the last version of AMQ broker supported on OpenShift 3.11.
Cloud Services
| AMQ broker 7.11 is supported as the following cloud services |
|---|
| Redhat Openshift Service on AWS (ROSA) |
| Microsoft Azure Redhat Openshift |
Note: When running the Broker in AWS it is recommended to use EBS storage instead of EFS. EFS was intended for large storage and not transactional processing and could lead to low throughput which in turn could cause the broker to become unresponsive.
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 and 2019 | v8.4.1 |
| PostgreSQL | 11.5 | v11 |
| Mysql | 8 | v8 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | --- | ✅ | ✅ | ✅ | ✅ |
| OpenWire | ✅ | --- | ✅ | ✅ | ✅ |
| CORE | ✅ | ✅ | --- | ✅ | ✅ |
| MQTT 5 | ✅ | ✅ | ✅ | --- | ✅ |
| STOMP | ✅ | ✅ | ✅ | ✅ | --- |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7. As AMQ 6 is coming to the end of its life it is strongly recommended that customers that have migrated from AMQ 6 to 7 migrate any remaining OpenWire clients to a modern supported client in one of the other actively supported clients.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 5 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.10 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.11 was built from source using Apache Maven 3.6.3. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.6.3.
Red Hat AMQ Broker 7.10
Every Red Hat AMQ Broker release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.
AMQ Broker 7.10 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 11, 17 |
| OracleJDK | 11 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.10 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 7 | x86_64 | OpenJDK 11 & 17 , Oracle JDK 11 |
| RHEL 8 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| RHEL 9 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11 & 17, Oracle JDK 11 |
- This is the last release that will be supported on RHEL 6 without a support exception
Note: Earlier versions of the JDK are not supported.
Interoperability with FUSE
With regards to FUSE, AMQ Broker 7.x is only supported as a remote broker. AMQ Broker 7.x is not certified to run as the internal broker in FUSE 6.x or 7.x. AMQ Broker 7.x has been tested and certified to work as an external broker with FUSE 6.x and 7.x components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility | Architecture |
|---|---|---|
| This content is not included.Red Hat AMQ Broker 7.10 | OpenShift 4.9,4.10, & 4.11 | x86_64,s390x, & ppc64le |
| This content is not included.Red Hat AMQ Broker Operator | OpenShift 4.9,4.10, & 4.11 | x86_64,s390x, & ppc64le |
Note: AMQ 7.8 is the last version of AMQ Broker supported on OpenShift 3.11.
Cloud Services
| AMQ Broker 7.10 is supported as the following cloud services |
|---|
| Redhat Openshift Service on AWS (ROSA) |
| Microsoft Azure Redhat Openshift |
Note: When running the Broker in AWS it is recommended to use EBS storage instead of EFS. EFS was intended for large storage and not transactional processing and could lead to low throughput which in turn could cause the broker to become unresponsive.
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 and 2019 | v8.4.1 |
| PostgreSQL | 11.5 | v11 |
| Mysql | 8 | v8 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 5 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7. As AMQ 6 is coming to the end of its life it is strongly recommended that customers that have migrated from AMQ 6 to 7 migrate any remaining OpenWire clients to a modern supported client in one of the other actively supported clients.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 5 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.10 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.10 was built from source using Apache Maven 3.6.3. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.6.3.
Red Hat AMQ Clients 2.11
AMQ Clients are supported for use on the following operating systems, architectures, and JVM versions. Note: Clients are backward compatible and supported on the latest released and supported version of AMQ 6.
Not all clients are supported on all operating systems. Specific client support is documented in the section titled Specific supported clients and OSs.
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 8 | X86_64 | OpenJDK 11 &17, Oracle JDK 11, IBM JDK 11 |
| RHEL 7 | x86_64 | OpenJDK 11 &17, Oracle JDK 11, or IBM JDK 11 |
| IBM AIX 7.1 | x86_64 | IBM JDK 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 11 |
| Microsoft Windows Server 2016 | x86_64 | Oracle JDK 11 |
| Microsoft Windows 10 Professional | x86_64 | Oracle JDK 11 |
| Solaris 10 and 11 | x86, x86_64, or Sparc 64 | Oracle JDK 11 |
Note: Earlier versions of the JDK are not supported.
Specific supported clients and OSs
The table below lists the supported operating systems for each AMQ Client. Additional information about specific clients is documented in subsequent sections.
| Operating system | AMQ JMS | AMQ C++ | AMQ JavaScript | AMQ Python | AMQ .NET | AMQ Ruby |
|---|---|---|---|---|---|---|
| RHEL 8 x86_64 | Yes | Yes | Yes | Yes | Yes | Yes |
| RHEL 7 x86_64 | Yes | Yes | Yes | Yes | Yes | Yes |
| Microsoft Windows Server 2012 R2 | Yes | Yes | Yes | Yes | Yes | No |
| Microsoft Windows Server 2016 | Yes | Yes | Yes | Yes | Yes | No |
| Microsoft Windows 10 Professional | Yes | Yes | Yes | Yes | Yes | No |
| IBM AIX 7.1 | Yes | No | No | No | No | No |
| Solaris 10 and 11 | Yes | No | No | No | No | No |
AMQ JMS details
The AMQ JMS client is supported on the following OSs and JVMs.
| Operating system | JVM |
|---|---|
| RHEL 8 | OpenJDK 11 &17, Oracle JDK 11, IBM JDK 11 |
| RHEL 7 | OpenJDK 11 &17 or Oracle JDK 11, IBM JDK 11 |
| Microsoft Windows Server 2012 R2 | Oracle JDK 11 |
| IBM AIX 7.1 | IBM JDK 11 |
| Solaris 10 and 11 | Oracle JDK 8 |
Notes:
- Earlier versions of the JDK are not supported.
- The AMQ JMS Client supports the use of the AMQ Pool library.
Standards and network protocols
- Version 2.0 of the Content from jcp.org is not included.Java Message Service API
- Version 1.0 of the Content from www.amqp.org is not included.Advanced Message Queueing Protocol (AMQP)
- Version 1.0 of the AMQP JMS Mapping
- Modern Content from tools.ietf.org is not included.TCP with Content from tools.ietf.org is not included.IPv6
AMQ C++ details
The AMQ C++ client is supported on the following OSs with the compilers and standards that are listed.
| Operating system | Compiler | Standard |
|---|---|---|
| RHEL 8 | GNU C++ | Compiling as C++11 |
| RHEL 7 | GNU C++ | Compiling as C++11 |
| Microsoft Windows Server 2012 R2 | Microsoft Visual Studio 2013 | Compiling as C++11 |
| Microsoft Windows Server 2016 | Microsoft Visual Studio 2013 | Compiling as C++11 |
| Microsfot Windows 10 Professional | Microsoft Visual Studio 2013 | Compiling as C++11 |
Standards and network protocols
- Version 1.0 of the Content from www.amqp.org is not included.Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Content from tools.ietf.org is not included.Transport Layer Security (TLS) protocol, the successor to SSL
- Modern Content from tools.ietf.org is not included.TCP with Content from tools.ietf.org is not included.IPv6
AMQ JavaScript details
The AMQ JavaScript client is supported on the following OSs and JavaScript runtimes.
| Operating system | JavaScript runtime |
|---|---|
| RHEL 8 | Node.js 14 |
| RHEL 7 | Node.js 14 from Software Collections |
| Microsoft Windows Server 2012 R2 | Node.js 14 from the Node.js project |
| Microsoft Windows Server 2016 | Node.js 14 from the Node.js project |
| Microsoft Windows 10 | Node.js 14 from the Node.js project |
Standards and network protocols
- Version 1.0 of the Content from www.amqp.org is not included.Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Content from tools.ietf.org is not included.Transport Layer Security (TLS) protocol, the successor to SSL
- Modern Content from tools.ietf.org is not included.TCP with Content from tools.ietf.org is not included.IPv6
Supported browsers
Supported browsers include the following:
- Google Chrome
- Mozilla Firefox
Note: Microsoft Internet Explorer is no longer supported for use with Broker consoles.
AMQ Python details
The AMQ Python client is supported on the following OSs and languages.
| Operating system | Python version |
|---|---|
| RHEL 8 | Python 3.6 |
| RHEL 7 | Python 3.6 |
| Microsoft Windows Server 2012 R2 | Python 3.6 or 3.8 |
| Microsoft Windows Server 2016 | Python 3.6 or 3.8 |
| Microsoft Windows 10 Professional | Python 3.6 or 3.8 |
Standards and network protocols
- Version 1.0 of the Content from www.amqp.org is not included.Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Content from tools.ietf.org is not included.Transport Layer Security (TLS) protocol, the successor to SSL
- Modern Content from tools.ietf.org is not included.TCP with Content from tools.ietf.org is not included.IPv6
AMQ .NET details
The AMQ .NET client is supported with the following OS and runtime.
| Operating system | .NET version |
|---|---|
| RHEL 8 | .NET Core 3.1 |
| RHEL 7 | .NET Core 3.1 |
| Microsoft Windows Server 2012 R2 | .NET Core 3.1 or .NET Framework 4.7 |
| Microsoft Windows Server 2016 | .NET Core 3.1 or .NET Framework 4.7 |
| Microsoft Windows 10 Professional | .NET Core 3.1 or .NET Framework 4.7 |
- Note .NET Core is not supported by the NMS client
Standards and network protocols
- Version 1.0 of the Content from www.amqp.org is not included.Advanced Message Queueing Protocol (AMQP)
- Modern Content from tools.ietf.org is not included.TCP with Content from tools.ietf.org is not included.IPv6
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
XA Transaction support
The following clients support XA transactions.
| Client | Wire Protocol |
|---|---|
| AMQ Core Protocol JMS | Core Protocol |
| AMQ OpenWire JMS | OpenWire Protocol |
AMQ Pool Support
The following clients support the use of the AMQ Pool library
- AMQ JMS Client
- AMQ Core Protocol JMS
- AMQ OpenWire JMS
Note: The AMQ Pool library is supported with these clients when used on OS and JVM combinations that are supported by the client.
Red Hat AMQ Online 1.7
This content is not included.Previous AMQ Online Releases
Red Hat AMQ Online 1.7 is supported on the following platforms.
| Platform | Version |
|---|---|
| OpenShift Container Platform | 3.11, 4.8 thru 4.10* |
- OpenShift 4.10 is the last release that AMQ Online will be supported on.
AMQ Online is no longer actively developed and will reach its end of life soon. This content is not included.AMQ Online EOL Statement
AMQ Broker 7.9 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.9 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
- This is the last release that will be supported on RHEL 6 without a support exception
Note: Earlier versions of the JDK are not supported.
Interoperability with FUSE
With regards to FUSE AMQ 7.9 Broker is only supported as a stand-alone broker. AMQ 7.8 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.7 has been tested and certified to work as an external broker with FUSE 6.X and 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.9 | OpenShift 4.6, 4.7, 4.8, 4.9, & 4.10 |
| This content is not included.Red Hat AMQ Broker Operator | OpenShift 4.6, 4.7, 4.8, 4.9, & 4.10 |
Note: AMQ 7.8 is the last version of AMQ Broker supported on OpenShift 3.11 AMQ Broker 7.8 is designated as a long term supported version
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 and 2019 | v6.4 |
| PostgreSQL | 11.5 | v11 |
| Mysql | 8 | v8 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.9 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.9 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
__
Red Hat AMQ Broker 7.8
Every Red Hat AMQ Broker release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.
Red Hat AMQ 7.8 is a long term supported version and all patches or defect fixes from z-stream releases for the next year will be applied to AMQ 7.8
AMQ Broker 7.8 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.8 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 * | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 * | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
- This is the last release that will be supported on RHEL 6 without a support exception
Note: Earlier versions of the JDK are not supported.
Interoperability with FUSE
With regards to FUSE AMQ 7.8 Broker is only supported as a stand-alone broker. AMQ 7.8 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.7 has been tested and certified to work as an external broker with FUSE 6.X and 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.8 | Versions 3.11, 4.6 and 4.7 |
| This content is not included.Red Hat AMQ Broker Operator | Versions 3.11, 4.6 and 4.7 |
Note: Beginning after AMQ 7.8 only Long Term Support releases of the broker will be supported on OpenShift 3.11
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 and 2019 | v6.4 |
| PostgreSQL | 11.5 | v11 |
| Mysql | 8 | v8 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.8 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.8 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
Red Hat AMQ Broker 7.7
Every Red Hat AMQ Broker release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.
AMQ Broker7.7 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.7 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 * | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 * | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
- RHEL 6 only supported on long term support versions
Note: Earlier versions of the JDK are not supported.
Interoperability with FUSE
With regards to FUSE AMQ 7.7 Broker is only supported as a stand-alone broker. AMQ 7.7 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.7 has been tested and certified to work as an external broker with FUSE 6.X and 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.7 | Version 4.5 and 4.6 |
| This content is not included.Red Hat AMQ Broker Operator | Version 4.5 and 4.6 |
Note: OpenShift 3.11 is only supported with Long Term Support Versions of AMQ (LTS) Broker and Operator before AMQ 7.8
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c, 18c, 19c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 | v6.4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.8 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.7 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
__
Red Hat AMQ Broker
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ Broker7.6 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.6 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.6 is only supported as a stand-alone broker.
AMQ 7.6 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.6 has been tested and certified to work as an external broker with FUSE 6.X and 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.6 | Version 3.11 and Newer |
| This content is not included.Red Hat AMQ Broker Operator | Version 3.11 and Newer |
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 | v6.4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.4 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.6 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
AMQ 7.5 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.5 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.5 is only supported as a stand-alone broker.
AMQ 7.5 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.5 has been tested and certified to work as an external broker with FUSE 6.X and 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.5 | Version 3.11 and Newer |
| This content is not included.Red Hat AMQ Broker Operator | Version 3.11 and Newer |
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 | v6.4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.4 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
- Ceph
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.5 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
__
Red Hat AMQ Broker 7.4
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ 7.4 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK | 8, 11 |
| OracleJDK | 8, 11 |
| IBM JDK | 8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
AMQ 7.4 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8 & 11 , Oracle JDK 8 & 11, IBM JDK 8 |
| RHEL 8 | x86_64 | OpenJDK 8 & 11, Oracle JDK 8 & 11 |
| Microsoft Windows Server 2012 R2 | x86_64 | OpenJDK 11, Oracle JDK 8 & 11 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.4 is only supported as a stand-alone broker.
AMQ 7.4 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7.4 has been tested and certified to work as an external broker with FUSE 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.4 | Version 3.11 and Newer |
| This content is not included.Red Hat AMQ Broker Operator (Technical Preview - DEPRECATED) | Version 3.11 and Newer |
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c | v12 |
| DB2 | 11 | v4 |
| MSSQL | 2016 | v6.4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.4 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.4 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
__
Red Hat AMQ Broker 7.3
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ 7.3 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK [2] | 1.8 |
| OracleJDK | 1.8 |
| IBM JDK | 1.8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
[2] Open JDK is only supported on RHEL.
AMQ 7.3 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.3 is only supported as a stand-alone broker. It has not be certified with EAP at the time of this release.
AMQ 7.3 is not certified to run as the internal broker in FUSE 6.X or 7.X.. AMQ 7 has been tested and certified to work as an external broker with FUSE 7.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.3 | Version 3.9 and Newer |
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c | v12 |
| DB2 | 11 | v4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.3 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.3 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
__
Red Hat AMQ Broker 7.2
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ 7.2 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK [2] | 1.8 |
| OracleJDK | 1.8 |
| IBM JDK | 1.8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
[2] Open JDK is only supported on RHEL.
AMQ 7.2 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.2 is only supported as a stand-alone broker. It has not be certified with EAP 7.0 or earlier. It is planned to be tested both as the internal broker of EAP 7.1 and as an external broker with EAP.
AMQ 7.2 is not certified to run as the internal broker in FUSE 6.X. AMQ 7 has been tested and certified to work as an external broker with FUSE 6.X components (camel-jms, camel-amqp).
OpenShift Images
| Image | OpenShift Compatibility |
|---|---|
| This content is not included.Red Hat AMQ Broker 7.2 | Version 3.9 and Newer |
Tested databases
| Database | Version | JDBC Driver Version |
|---|---|---|
| Oracle | 12c | v12 |
| DB2 | 11 | v4 |
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT 3.1.1 | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. AMQ 7 Brokers support version MQTT 3.1.1 with Qos levels of 0,1, & 2 Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.2 in the master/slave failover configuration:
- NFSv4
- GFS2
- GlusterFS *
Note: GlusterFS is supported for use as the message store for brokers in OpenShift and "bare metal," environments. GlusterFS is not recommended or supported for creating multiple-datacenter/availability zone DR strategies.
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.2 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
Red Hat AMQ Broker 7.1
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ 7.1 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK [2] | 1.8 |
| OracleJDK | 1.8 |
| IBM JDK | 1.8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
[2] Open JDK is only supported on RHEL.
AMQ 7.1 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7.1 is only supported as a stand-alone broker. It has not be certified with EAP 7.0 or earlier. It is planned to be tested both as the internal broker of EAP 7.1 and as an external broker with EAP.
AMQ 7.1 is not certified to run as the internal broker in FUSE 6.X. AMQ 7 has been tested and certified to work as an external broker with FUSE 6.X components (camel-jms, camel-amqp).
Tested databases
The Oracle 12c database and Oracle JDBC Driver v12 database driver are supported for use with the AMQ Broker.
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.0 in the master/slave failover configuration:
- NFSv4
- GFS2
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Microsoft Windows Server 2012 R2 Active Directory
- Free IPA (Red Hat Identity Management) 4.5.0-21
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Directory
- Apache Directory Server
- RH 389 Directory Server
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Apache Maven
AMQ 7.1 was built from source using Apache Maven 3.2.5. It should not be assumed that building from source with an earlier version will work. Any examples provided with the broker should be built or executed with Maven 3.2.5.
Red Hat AMQ Broker 7.0
Every Red Hat JBoss® AMQ (JBoss AMQ) release is tested and supported on a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations. Red Hat provides both production and development support for supported configurations and tested integrations according to your subscription agreement in both physical and virtual environments.[1]
AMQ 7 Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments.[1] In order to be running in a supported configuration, JBoss AMQ must be running in one of the following JVM versions and on one of the operating systems supported by that JVM.
| Java Virtual Machine | Version |
|---|---|
| OpenJDK [2] | 1.8 |
| OracleJDK | 1.8 |
| IBM JDK | 1.8 |
[1] Red Hat expects that customers will remain on a supported environment. In the event that a JVM, operating system, database, etc., or its version is no longer supported by its vendor, Red Hat may be limited in its ability to provide support and may require you to reproduce the issue in a supported environment for continued assistance.
[2] Open JDK is only supported on RHEL.
AMQ 7 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations
| Operating system | Architecture | JVM |
|---|---|---|
| RHEL 6 | x86 | OpenJDK 8, Oracle JDK 8 |
| RHEL 6 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Container Interoperability
Currently AMQ 7 is only supported as a stand-alone broker. It has not be certified with EAP 7.0 or earlier. It is planned to be tested both as the internal broker of EAP 7.1 and as an external broker with EAP.
AMQ 7 is not certified to run as the internal broker in FUSE 6.X. AMQ 7 has been tested and certified to work as an external broker with FUSE 6.X components (camel-jms, camel-amqp).
Tested databases
The Oracle 12c database and Oracle JDBC Driver v12 database driver are supported for use with the AMQ Broker.
Note: Databases are only required when JDBC is selected as the message persistence store option. Please read documentation to understand the limitations and performance trade-offs inherent in using JDBC persistence.
Message wire-protocol conversion support
Messages sent to an address from a client that uses one wire-protocol should be consumable from a client using one of the other supported wire protocols as listed below.
| Protocol | AMQP 1.0 | OpenWire | CORE | MQTT | STOMP |
|---|---|---|---|---|---|
| AMQP 1.0 | NA | X | X | X | X |
| OpenWire | X | NA | X | X | X |
| CORE | X | X | NA | X | X |
| MQTT | X | X | X | NA | X |
| STOMP | X | X | X | X | NA |
- AMQP 1.0 is the message protocol of the AMQ JMS, AMQ C++, AMQ JavaScript, AMQ Python, and AMQ .NET clients.
- OpenWire is the message protocol of the AMQ OpenWire JMS client, the JMS implementation previously provided in AMQ 6. It is provided for backward compatibility during migration from AMQ 6 to AMQ 7.
- Core Protocol is the message protocol of the AMQ Core Protocol JMS client, the JMS implementation previously provided with HornetQ.
- MQTT is a machine to machine messaging protocol commonly used in IoT applications. Red Hat does not provide clients for use with the MQTT protocol. Several MQTT clients for multiple languages can be found at the Content from mqtt.org is not included.MQTT Community.
- STOMP is a simple text based protocol for sending messages through a broker. Red Hat does not provide clients for STOMP. For information about using STOMP visit the Content from stomp.github.io is not included.STOMP site.
A Note on shared - nothing high availability
Shared - nothing HA is only supported in a single local data center preferably on the same network subnet. Shared - nothing HA is very sensitive to network latency and consistency therefore shared - nothing HA configurations where the master is in one data center and the slave is in another are specifically not supported.
Supported network file systems
The following network file systems are supported for use with AMQ Broker 7.0 in the master/slave failover configuration:
- NFSv4
- GFS2
LDAP Directories tested for use with the broker
The following LDAP providers were tested as users stores for authentication and authorization
- Windows Active Director
- Apache Directory Server