Red Hat JBoss A-MQ Supported Configurations
Every Red Hat JBoss® A-MQ (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]
For AMQ 7 Please see this article.
**A note on AMQ 6 images and OpenShift. AMQ 6 Images are not supported on OCP 4.X. AMQ 6 images are supported on OCP 3.9 and 3.11.
A-MQ 6.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 A-MQ 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.7 1.8 |
| Oracle JDK | 1.7 1.8 |
| IBM JDK | 1.7 1.8 |
| HP JVM | 1.7 1.8 |
A-MQ 6.3 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations.
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Red Hat Enterprise Linux 6 (latest update) | x86 | Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Red Hat Enterprise Linux 6 (latest update) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x |
| Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.8.x |
| Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.8.x |
| IBM AIX 7.1 | Power ISA v.2.06 | IBM JDK 1.7.x IBM JDK 1.8.x |
| HP-UX 11i | IA64 | HP JVM 1.7.x HP JVM 1.8.x |
A-MQ 6.3 Tested Integrations
Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss A-MQ release. This list of tested integrations will expand over time.
Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
The following databases and database drivers were tested as part of the latest JBoss A-MQ 6 release.
| Databases | JDBC Driver |
|---|---|
| Oracle 12c | Oracle JDBC Driver v12 |
| Oracle RAC | Oracle JDBC Driver v12 |
| MySQL 5.6 | MySQL Connector/J 5 |
| Microsoft SQL Server 2008 | MS SQL Server JDBC Driver 3 |
| Microsoft SQL Server 2012 | MS SQL Server JDBC Driver 4 |
| Microsoft SQL Server 2014 | MS SQL Server JDBC Driver 4 |
| PostgreSQL 9.3.5 | JDBC 4 Postgresql Driver, Version 9 |
| IBM DB2 9.7 | IBM DB2 JDBC Universal Driver Architecture 4.9.78 |
The following integrations are also supported in JBoss Fuse 6.3:
| Integration | Version |
|---|---|
| Red Hat Enterprise Linux High Availability | See Red Hat Enterprise Linux tested configurations |
JBoss A-MQ 6.3 Container Interoperability
The JBoss A-MQ core broker component (based on Apache ActiveMQ) is supported on other JBoss containers. Components that are supported on other containers are provided in the /extras directory of the JBoss A-MQ distribution for your convenience. Note: For these configurations to be supported a subscription to both JBoss A-MQ and the supported container is required.
| A-MQ Component | Version | JBoss Container | Version |
|---|---|---|---|
| ActiveMQ (connector only - not embedded) | 5.11.0.redhat | EAP | 6.4 7.0 |
JBoss A-MQ 6.3 Supported Network Filesystems
In JBoss A-MQ 6.3, the following network filesystems are supported for use with the master/slave failover feature:
- NFSv4
- GFS2
- CIFS/SMB (on Windows)
A-MQ 6.2 and 6.2.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 A-MQ 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.7 1.8 |
| Oracle JDK | 1.7 1.8 |
| IBM JDK | 1.7 1.8 |
| HP JVM | 1.7 |
A-MQ 6.2 and 6.2.1 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations.
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 7 (latest update) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Red Hat Enterprise Linux 6 (latest update) | x86 | Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Red Hat Enterprise Linux 6 (latest update) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x IBM JDK 1.7.x IBM JDK 1.8.x OpenJDK 1.7.x OpenJDK 1.8.x |
| Red Hat Enterprise Linux 5 (latest update) (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x Oracle JDK 1.8.x OpenJDK 1.7.x |
| Microsoft Windows Server 2012 R2 | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.8.x |
| Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.8.x |
| Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.8.x |
| IBM AIX 7.1 | Power ISA v.2.06 | IBM JDK 1.7.x IBM JDK 1.8.x |
| HP-UX 11i | IA64 | HP JVM 1.7.x |
A-MQ 6.2 and 6.2.1 Tested Integrations
Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss A-MQ release. This list of tested integrations will expand over time.
Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
The following databases and database drivers were tested as part of the latest JBoss A-MQ 6 release.
| Databases | JDBC Driver |
|---|---|
| Oracle 12c | Oracle JDBC Driver v12 |
| Oracle RAC | Oracle JDBC Driver v12 |
| MySQL 5.6 | MySQL Connector/J 5 | Microsoft SQL Server 2008 | Microsoft SQL Server JDBC Driver 3 |
| PostgreSQL 9.3.5 | JDBC 4 Postgresql Driver, Version 9 |
The following integrations are also supported in JBoss Fuse 6.2 and 6.2.1:
| Integration | Version |
|---|---|
| Red Hat Enterprise Linux High Availability | See Red Hat Enterprise Linux tested configurations |
JBoss A-MQ 6.2 and 6.2.1 Container Interoperability
The JBoss A-MQ core broker component (based on Apache ActiveMQ) is supported on other JBoss containers. Components that are supported on other containers are provided in the "/extras" directory of the JBoss A-MQ distribution for your convenience. Note: For these configurations to be supported a subscription to both JBoss A-MQ and the supported container is required.
| A-MQ Component | Version | JBoss Container | Version |
|---|---|---|---|
| ActiveMQ (connector only - not embedded) | 5.11.0.redhat | EAP | 6.1.1, 6.2, 6.3, 6.4 |
JBoss A-MQ 6.2 and 6.2.1 Supported Network Filesystems
In JBoss A-MQ 6.2, the following network filesystems are supported for use with the master/slave failover feature:
- NFSv4
- GFS2
A-MQ 6.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 A-MQ 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.7 1.6 (deprecated) |
| Oracle JDK | 1.7 1.6 (deprecated) |
| IBM JDK | 1.7 1.6 (deprecated) |
A-MQ 6.1 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations.
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 6 (latest update) | x86 x86_64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated) |
| Red Hat Enterprise Linux 5 (latest update) (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated) |
| Microsoft Windows 2008 Server R2 (deprecated) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| IBM AIX 7.1 | pSeries | IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) |
A-MQ 6.1 Tested Integrations
Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss A-MQ release. This list of tested integrations will expand over time.
Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
The following databases and database drivers were tested as part of the latest JBoss A-MQ 6 release.
| Databases | JDBC Driver |
|---|---|
| Oracle 11g | Oracle JDBC Driver v11 |
| MySQL 5.1 | MySQL Connector/J 5 |
| MySQL 5.5 | MySQL Connector/J 5 | Microsoft SQL Server 2008 | Microsoft SQL Server JDBC Driver 3 |
| PostgreSQL 8.4 | JDBC4 Postgresql Driver, Version 8 |
| PostgreSQL 9.1 | JDBC4 Postgresql Driver, Version 9 |
JBoss A-MQ 6.1 Container Interoperability
The JBoss A-MQ core broker component (based on Apache ActiveMQ) is supported on other JBoss containers. Components that are supported on other containers are provided in the "/extras" directory of the JBoss A-MQ distribution for your convenience. Note: For these configurations to be supported a subscription to both JBoss A-MQ and the supported container is required.
| A-MQ Component | Version | JBoss Container | Version |
|---|---|---|---|
| ActiveMQ (connector only - not embedded) | 5.9.0.redhat | EAP | 6.1.1, 6.2, 6.3 |
JBoss A-MQ 6.1 Supported Network Filesystems
In JBoss A-MQ 6.2, the following network filesystems are supported for use with the master/slave failover feature:
- NFSv4
- GFS2
JBoss A-MQ 6.1 CMS and NMS Clients
The C++ Messaging Service (CMS) client and the .Net Messaging Service (NMS) client have been tested as follows:
- CMS Client: has been tested on Linux using gcc 4+ and on Windows 7 with VS2010.
- NMS Client: has been tested using Mono on Linux and on a Windows XP VM using the platform SDK kit with command line tools to test on .NET 2.0, 3.5 and 4.0.
A-MQ 6.0 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 A-MQ 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.7 1.6 (deprecated) |
| Oracle JDK | 1.7 1.6 (deprecated) |
| IBM JDK | 1.7 1.6 (deprecated) |
A-MQ 6.0 Tested Configurations
Red Hat has performed the full range of platform tests on the following tested configurations.
| Operating System | Chipset Architecture | Java Virtual Machine |
|---|---|---|
| Red Hat Enterprise Linux 6 (latest update) | x86 x86_64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated) |
| Red Hat Enterprise Linux 5 (latest update) (deprecated) | x86 x86_64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) OpenJDK 1.7.x OpenJDK 1.6.x (deprecated) |
| Microsoft Windows 2008 Server R2 (deprecated) | x86_64 | Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| Oracle Solaris 10 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| Oracle Solaris 11 | x86 x86_64 SPARC64 |
Oracle JDK 1.7.x Oracle JDK 1.6.x (deprecated) |
| IBM AIX 7.1 | pSeries | IBM JDK 1.7.x IBM JDK 1.6.x (deprecated) |
A-MQ 6.0 Tested Integrations
Tested Integrations are a defined set of specifically tested integrating technologies that represent the most common combinations that JBoss Enterprise Middleware customers are using. For these integrations, Red Hat has directly, or through certified partners, exercised our full range of platform tests as part of the product release process. Issues identified as part of this testing process are highlighted in release notes for each JBoss A-MQ release. This list of tested integrations will expand over time.
Red Hat provides both production and development support for the tested integrations in the same major version family at or above the tested version according to your subscription agreement. Earlier versions of a tested integration in the same major version family are supported on a commercially reasonable basis.
The following databases and database drivers were tested as part of the latest JBoss A-MQ 6 release.
| Databases | JDBC Driver |
|---|---|
| Oracle 11g | Oracle JDBC Driver v11 |
| MySQL 5.1 | MySQL Connector/J 5 |
| MySQL 5.5 | MySQL Connector/J 5 | Microsoft SQL Server 2008 | Microsoft SQL Server JDBC Driver 3 |
| PostgreSQL 8.4 | JDBC4 Postgresql Driver, Version 8 |
| PostgreSQL 9.1 | JDBC4 Postgresql Driver, Version 9 |
[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] Red Hat limits support of OpenJDK to Red Hat Enterprise Linux.
For a list of changes to this document follow this link.
JBoss A-MQ 6.0 Supported Network Filesystems
In JBoss A-MQ 6.2, the following network filesystems are supported for use with the master/slave failover feature:
- NFSv4
- GFS2
Comments