Red Hat AMQ 7 Supported Configurations
Table of Contents
__
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 |
|---|---|
| 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 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 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 sensative 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 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 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 sensative 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 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 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 sensative 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
- RH 389 Directory Server
Red Hat AMQ Interconnect 1.2
AMQ Interconnect is supported for use with the following operating systems and architectures.
| Operating system | Architecture |
|---|---|
| RHEL 6 | x86 or x86_64 |
| RHEL 7 | x86_64 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with IPv6
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Free IPA (Red Hat Identity Management) 4.5.0-21
Red Hat AMQ Interconnect 1.1
AMQ Interconnect is supported for use with the following operating systems and architectures.
| Operating system | Architecture |
|---|---|
| RHEL 6 | x86 or x86_64 |
| RHEL 7 | x86_64 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with IPv6
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Free IPA (Red Hat Identity Management) 4.5.0-21
Red Hat AMQ Interconnect 1.0
AMQ Interconnect is supported for use with the following operating systems and architectures.
| Operating system | Architecture |
|---|---|
| RHEL 6 | x86 or x86_64 |
| RHEL 7 | x86_64 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with IPv6
Kerberos Network Authentication Service
Kerberos version 5 is supported for authentication between kerberos enabled clients and the broker. Kerberos was tested with the following.
- Free IPA (Red Hat Identity Management) 4.5.0-21
Red Hat AMQ Clients 2.1
AMQ Clients are supported for use on the following operating systems, architectures, and JVM versions.
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 6 | x86 | OpenJDK 8 or Oracle JDK 8 |
| RHEL 6 or 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| HP-UX 11i | x86_64 | HP JVM 8 |
| IBM AIX 7.1 | x86_64 | IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
| Solaris 10 and 11 | x86, x86_64, or Sparc 64 | Oracle JDK 8 |
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 7 | Yes | Yes | Yes | Yes | No | Yes |
| RHEL 6 | Yes | Yes | Yes | Yes | No | No |
| Microsoft Windows Server 2012 R2 | Yes | Yes | Yes | No | Yes | No |
| HP-UX 11i | Yes | No | No | No | No | No |
| IBM AIX 7.1 | Yes | No | No | No | No | No |
| Solaris 10 and 11 | Yes | No | No | No | No | No |
*Developer Preview only not suitable for production use.
AMQ JMS details
The AMQ JMS client is supported on the following OSs and JVMs.
| Operating system | JVM |
|---|---|
| RHEL 6 and 7 | OpenJDK 8 or Oracle JDK 8 |
| Microsoft Windows Server 2012 R2 | Oracle JDK 8 |
| HP-UX 11i | HP-UX JVM 8 |
| IBM AIX 7.1 | IBM JDK 8 |
| Solaris 10 and 11 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Standards and network protocols
- Version 2.0 of the Java Message Service API
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Version 1.0 of the AMQP JMS Mapping
- Modern TCP with 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 6 (64 bit only) and 7 | GNU C++ | Compiling as C++03 or C++11 |
| Microsoft Windows Server 2012 R2 | Microsoft Visual Studio 2013 | Compiling as C++03 or C++11 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ JavaScript details
The AMQ JavaScript client is supported on the following OSs and JavaScript runtimes.
| Operating system | JavaScript runtime |
|---|---|
| RHEL 6 (64 bit only) | Node.js 4, 6, & 8 from Software Collections |
| RHEL 7 | Node.js 4, 6, & 8 from Software Collections |
| Microsoft Windows Server 2012 R2 | Node.js 4, 6, & 8 from the Node.js project |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
Supported browsers
Supported browsers include the following:
- Google Chrome
- Microsoft Internet Explorer
- Mozilla Firefox
AMQ Python details
The AMQ Python client is supported on the following OSs and languages.
| Operating system | Python version |
|---|---|
| RHEL 6 and 7 | Python 2.6 or 2.7 |
| Microsoft Windows Server 2012 R2 | Python 2.7 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ .NET details
The AMQ .NET client is supported with the following OS and runtime.
| Operating system | .NET version |
|---|---|
| Microsoft Windows Server 2012 R2 | .NET Framework 4.5, .NET Core 2.0 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with 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 JMS | Core Protocol |
| AMQ OpenWire | OpenWire Protocol |
Red Hat AMQ Clients 2.0
AMQ Clients are supported for use on the following operating systems, architectures, and JVM versions.
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 6 | x86 | OpenJDK 8 or Oracle JDK 8 |
| RHEL 6 or 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| HP-UX 11i | x86_64 | HP JVM 8 |
| IBM AIX 7.1 | x86_64 | IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
| Solaris 10 and 11 | x86, x86_64, or Sparc 64 | Oracle JDK 8 |
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 7 | Yes | Yes | Yes | Yes | No | Yes |
| RHEL 6 | Yes | Yes | Yes | Yes | No | No |
| Microsoft Windows Server 2012 R2 | Yes | Yes | Yes | No | Yes | No |
| HP-UX 11i | Yes | No | No | No | No | No |
| IBM AIX 7.1 | Yes | No | No | No | No | No |
| Solaris 10 and 11 | Yes | No | No | No | No | No |
*Developer Preview only not suitable for production use.
AMQ JMS details
The AMQ JMS client is supported on the following OSs and JVMs.
| Operating system | JVM |
|---|---|
| RHEL 6 and 7 | OpenJDK 8 or Oracle JDK 8 |
| Microsoft Windows Server 2012 R2 | Oracle JDK 8 |
| HP-UX 11i | HP-UX JVM 8 |
| IBM AIX 7.1 | IBM JDK 8 |
| Solaris 10 and 11 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Standards and network protocols
- Version 2.0 of the Java Message Service API
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Version 1.0 of the AMQP JMS Mapping
- Modern TCP with 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 6 (64 bit only) and 7 | GNU C++ | Compiling as C++03 or C++11 |
| Microsoft Windows Server 2012 R2 | Microsoft Visual Studio 2013 | Compiling as C++03 or C++11 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ JavaScript details
The AMQ JavaScript client is supported on the following OSs and JavaScript runtimes.
| Operating system | JavaScript runtime |
|---|---|
| RHEL 6 (64 bit only) | Node.js 4, 6, & 8 from Software Collections |
| RHEL 7 | Node.js 4, 6, & 8 from Software Collections |
| Microsoft Windows Server 2012 R2 | Node.js 4, 6, & 8 from the Node.js project |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
Supported browsers
Supported browsers include the following:
- Google Chrome
- Microsoft Internet Explorer
- Mozilla Firefox
AMQ Python details
The AMQ Python client is supported on the following OSs and languages.
| Operating system | Python version |
|---|---|
| RHEL 6 and 7 | Python 2.6 or 2.7 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ .NET details
The AMQ .NET client is supported with the following OS and runtime.
| Operating system | .NET version |
|---|---|
| Microsoft Windows Server 2012 R2 | .NET Framework 4.5, .NET Core 2.0 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with 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 JMS | Core Protocol |
| AMQ OpenWire | OpenWire Protocol |
Red Hat AMQ Clients 1.2
AMQ Clients are supported for use on the following operating systems, architectures, and JVM versions.
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 6 | x86 | OpenJDK 8 or Oracle JDK 8 |
| RHEL 6 or 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| RHEL 7 | x86_64 | OpenJDK 8, Oracle JDK 8, or IBM JDK 8 |
| HP-UX 11i | x86_64 | HP JVM 8 |
| IBM AIX 7.1 | x86_64 | IBM JDK 8 |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 8 |
| Solaris 10 and 11 | x86, x86_64, or Sparc 64 | Oracle JDK 8 |
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 |
|---|---|---|---|---|---|
| RHEL 6 and 7 | Yes | Yes | Yes | Yes | No |
| Microsoft Windows Server 2012 R2 | Yes | Yes | Yes | No | Yes |
| HP-UX 11i | Yes | No | No | No | No |
| IBM AIX 7.1 | Yes | No | No | No | No |
| Solaris 10 and 11 | Yes | No | No | No | No |
AMQ JMS details
The AMQ JMS client is supported on the following OSs and JVMs.
| Operating system | JVM |
|---|---|
| RHEL 6 and 7 | OpenJDK 8 or Oracle JDK 8 |
| Microsoft Windows Server 2012 R2 | Oracle JDK 8 |
| HP-UX 11i | HP-UX JVM 8 |
| IBM AIX 7.1 | IBM JDK 8 |
| Solaris 10 and 11 | Oracle JDK 8 |
Note: Earlier versions of the JDK are not supported.
Standards and network protocols
- Version 2.0 of the Java Message Service API
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Version 1.0 of the AMQP JMS Mapping
- Modern TCP with 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 6(64 bit only) & 7 | GNU C++ | Compiling as C++03 or C++11 |
| Microsoft Windows Server 2012 R2 | Microsoft Visual Studio 2013 | Compiling as C++03 or C++11 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ JavaScript details
The AMQ JavaScript client is supported on the following OSs and JavaScript runtimes.
| Operating system | JavaScript runtime |
|---|---|
| RHEL 6 (64 bit only) | Node.js 0.10 from Software Collections |
| RHEL 7 | Node.js 0.10 or Node.js 4 from Software Collections |
| Microsoft Windows Server 2012 R2 | Node.js 4 from the Node.js project |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
Supported browsers
Supported browsers include the following:
- Google Chrome
- Microsoft Internet Explorer
- Mozilla Firefox
AMQ Python details
The AMQ Python client is supported on the following OSs and languages.
| Operating system | Python version |
|---|---|
| RHEL 6 and 7 | Python 2.6 or 2.7 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Versions 1.0, 1.1, and 1.2 of the Transport Layer Security (TLS) protocol, the successor to SSL
- Modern TCP with IPv6
AMQ .NET details
The AMQ .NET client is supported with the following OS and runtime.
| Operating system | .NET version |
|---|---|
| Microsoft Windows Server 2012 R2 | .NET Framework 4.5 |
Standards and network protocols
- Version 1.0 of the Advanced Message Queueing Protocol (AMQP)
- Modern TCP with 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 JMS | Core Protocol |
| AMQ OpenWire | OpenWire Protocol |
Red Hat AMQ Console 1.0
In general, it is recommended that you use the latest available version of each browser type to ensure that you have the latest security updates and more. Each of the following browsers has been tested by using the latest version available at the time of this release:
- Google Chrome
- Microsoft Internet Explorer
- Mozilla Firefox
- Windows Edge
Red Hat AMQ Streams 1.0
AMQ Streams is currently supported on the following platforms:
| Platform | Version |
|---|---|
| OpenShift Container Platform | 3.9 and newer |
| Red Hat Container Developer Kit | * |
- Red Hat CDK is supported for development and evaluation only. Production support is not provided for AMQ Streams on the Red Hat CDK.
Supported Apache Kafka Ecosystem
AMQ Streams contains Apache Kafka which has a very large echosystem that included many client, connectors, and components that may be linked from the Apache Kafka project webpage. In this release only the java components released directly from the Apache Software Foundation are supported, specifically:
- Apache Kafka Broker
- Apache Kafka Connect
- Apache Kafka Streaming API
- Apache Kafka Java Producer, Consumer, and Management clients
- Apache Zookeeper *
*Apache Zookeeper supported ONLY as an implementation detail of Apache Kafka
Red Hat AMQ Streams for RHEL 1.0 Beta
AMQ Streams for RHEL 1.0 Beta is supported on the following platforms.
| Operating System | JVM |
|---|---|
| RHEL 7 | Open JDK 8 |
Supported Apache Kafka Ecosystem
AMQ Streams contains Apache Kafka which has a very large echosystem that included many client, connectors, and components that may be linked from the Apache Kafka project webpage. In this release only the java components released directly from the Apache Software Foundation are supported, specifically:
- Apache Kafka Broker
- Apache Kafka Connect
- Apache Kafka Streaming API
- Apache Kafka Java Producer, Consumer, and Management clients
- Apache Zookeeper *
*Apache Zookeeper supported ONLY as an implementation detail of Apache Kafka
