Every Red Hat Data Grid (RHDG) release is tested and supported on Red Hat OpenShift, as well as a variety of market-leading operating systems, Java™ Virtual Machines (JVMs), and database combinations.
Data Grid Operator for OpenShift
This section lists support details for the current version of Data Grid Operator. Previous versions of the Data Grid for OpenShift image are deprecated.
Red Hat supports Data Grid on the following versions of OpenShift Container Platform. However, you should always use the most recently available version of Red Hat OpenShift to take advantage of the latest features, capabilities, and security improvements.
| Data Grid Operator Version |
OpenShift Container Platform Version |
| Data Grid Operator 8.1 |
4.4, 4.5, 4.6 |
| Data Grid Operator 8.0 |
4.2 and 4.3 |
This article details the policy for support of Red Hat Middleware products on OpenShift.
This article provides full support details for running Red Hat Middleware products in containerized images.
Supported Configurations
Red Hat provides both production and development support for supported configurations according to your subscription agreement in both physical and virtual environments. In order to be running in a supported configuration, JDG must be running in one of the following JVM versions and on one of the operating systems supported by that JVM. Red Hat relies on the testing and certification process of the underlying JVM for platform compatibility. Red Hat limits support of OpenJDK to Red Hat Enterprise Linux.
Tested Configurations
Tested configurations are a defined set of validated and recommended operating systems, chip architectures, JVM, and database combinations. These represent the most common combinations that JBoss Enterprise Middleware customers are using.
Red Hat has performed the full range of platform tests on the following tested configurations.
Supported Configurations: Red Hat Data Grid 8.1 and 8.0
| Java Virtual Machine |
Version |
| OpenJDK |
1.8* and 11 |
| Oracle JDK |
1.8* and 11 |
| IBM JDK |
1.8* |
| Azul Zing |
1.8* |
- Data Grid Server is supported with Java 11
- Data Grid Embedded Mode is supported with Java 1.8 and Java 11
- Hot Rod Java Clients are supported with Java 1.8 and Java 11
Tested Configurations: Red Hat Data Grid 8.1
| Operating System and Chipset Architecture |
Open JDK |
| Red Hat Enterprise Linux 8 x86_64 |
1.8* and 11 |
| Windows Server 2019 |
1.8* and 11 |
- Data Grid Server is tested with Java 11 only
The following databases and database drivers were tested as part of the Red Hat Data Grid 8.1 release
| Database |
Version (JDBC Driver Version) |
| MySQL 8.0.12 |
MySQL Connector/J 8.0.18 |
| MariaDB 10.1.19 |
MariaDB Connector/J 2.4.4 |
| MariaDB Galera Cluster 10.1.19 |
MariaDB Connector/J 2.4.4 |
| IBM DB2 Enterprise e11.1 |
IBM DB2 JDBC Universal Driver Architecture 4.25.1301 |
| Oracle 19c RAC 19.3.0.0.0 |
Oracle JDBC Driver. With JDK11, use ojdbc8.jar or ojdbc10.jar version 19.6. With JDK8, use ojdbc8.jar version 19.3. |
| PostgreSQL 11.5 |
JDBC4 Postgresql Driver, Version 42.2.8 |
| Microsoft SQL Server 2017 |
Microsoft JDBC Drivers 7.4.1.0 (.jre8.jar) |
| Enterprise DB Postgres Plus Advanced Server 11.6 |
Postgres Plus Advanced Server Driver (42.2.8.1-1) |
| Sybase ASE 16.0 (SP02) |
Sybase JDBC driver v16 |
Embedded Mode has been tested in following containers
RHDG does not require an application server for runtime purposes, and RHDG is supported when deployed with applications in a supported JVM without a container. RHDG 8.1
| Application Container |
Version |
| JBoss Enterprise Application Platform 7 |
7.3.0 |
| JBoss Web Server (Tomcat 9) |
5.3.0 |
Using RocksDB as a cache store with RHDG 8.1 has been tested with the following
| Operating System and Chipset Architecture |
Open JDK |
| Red Hat Enterprise Linux 8 x86_64 |
1.8, 11 |
| Windows Server 2019 |
1.8, 11 |
The following products have also been tested for integration with RHDG 8.1
| Product |
Version |
| Spring |
5 |
| Spring Boot |
2.3.x with Spring 5 |
| LDAP |
Red Hat Directory Server 10, used for authentication |
The Red Hat Data Grid 8.1 Administration Console has been tested with the following browsers
| Browser |
Version |
Platform |
| Mozilla Firefox |
74.0 |
Linux |
Tested Configurations: Red Hat Data Grid 8.0
| Operating System and Chipset Architecture |
Open JDK |
| Red Hat Enterprise Linux 8 x86_64 |
1.8* and 11 |
| Red Hat Enterprise Linux 7 x86_64 |
1.8* and 11 |
- Data Grid Server is tested with Java 11 only
The following databases and database drivers were tested as part of the Red Hat Data Grid 8.0 release
| Database |
Version (JDBC Driver Version) |
| MySQL 8.0 |
MySQL Connector/J 8.0.18 |
| MariaDB 10.1.19 |
MariaDB Connector/J 2.4.4 |
| MariaDB Galera Cluster 10.1.19 |
MariaDB Connector/J 2.4.4 |
| IBM DB2 Enterprise e11.1 |
IBM DB2 JDBC Universal Driver Architecture 4.25.1301 |
| Oracle 19c RAC |
Oracle JDBC Driver v19.3.0.0 (ojdbc8.jar) |
| PostgreSQL 11.5 |
JDBC4 Postgresql Driver, Version 42.2.8 |
| Microsoft SQL Server 2017 |
Microsoft JDBC Drivers 7.4.1.0 (.jre8.jar) |
| Enterprise DB Postgres Plus Advanced Server 11.6 |
Postgres Plus Advanced Server Driver (42.2.8.1-1) |
| Sybase ASE 16.0 (SP02) |
Sybase JDBC driver v16 |
Embedded Mode has been tested in following containers
RHDG does not require an application server for runtime purposes, and RHDG is supported when deployed with applications in a supported JVM without a container. RHDG 8.0
| Application Container |
Version |
| JBoss Enterprise Application Platform 7 |
7.3.0 |
| JBoss Web Server (Tomcat 9) |
5.2.0 |
Using RocksDB as a cache store with RHDG 8.0 has been tested with the following
| Operating System and Chipset Architecture |
Open JDK |
| Red Hat Enterprise Linux 8 x86_64 |
1.8, 11 |
| Red Hat Enterprise Linux 7 x86_64 |
1.8, 11 |
The following products have also been tested for integration with RHDG 8.0
| Product |
Version |
| Spring |
4 and 5 |
| Spring Boot |
1.5.x with Spring 4 and 2.1.x with Spring 5 |
| LDAP |
Red Hat Directory Server 10, used for authentication |
The Red Hat Data Grid 8.0 Administration Console has been tested with the following browsers
| Browser |
Version |
Platform |
| Mozilla Firefox |
74.0 |
Linux |
5 Comments
Hi We currently use RHDG with EAP and would like to upgrade to EAP 7.3 / RHDG 8.0. Can you advise when the Red Hat JBoss Data Grid 8.0 Modules for JBoss EAP will be available please ? Kind Regards
Hello David, EAP modules will not continue, the plan is to integrate RHDG directly with EAP and make it possible to use the functionallity without additional installation. If you have current issues and questions it would be better to open a support case, please mention that the case should be owned by me, as I'm the Product Lead for this and will work on this.
Thanks Wolf-Dieter Support case opened: https://access.redhat.com/support/cases/#/case/02635056
if i try to enable the ssl server identity on open jdk 1.8 i get below error. i also have a case opened on the same https://access.redhat.com/support/cases/#/case/02722079
19:57:33,091 WARN (SINGLE_PORT-ServerIO-6-1) [io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. io.netty.handler.codec.DecoderException: java.lang.RuntimeException: ALPN unsupported. Is your classpath configured correctly? For Conscrypt, add the appropriate Conscrypt JAR to classpath and set the security provider. For Jetty-ALPN, see http://www.eclipse.org/jetty/documentation/current/alpn-chapter.html#alpn-starting at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:468) at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:401) at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:368) at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:351) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:260) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:246) at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:239) at io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:260) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:246) at io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901) at io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:818) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472) at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.RuntimeException: ALPN unsupported. Is your classpath configured correctly? For Conscrypt, add the appropriate Conscrypt JAR to classpath and set the security provider. For Jetty-ALPN, see http://www.eclipse.org/jetty/documentation/current/alpn-chapter.html#alpn-starting at io.netty.handler.ssl.JdkAlpnApplicationProtocolNegotiator$FailureWrapper.wrapSslEngine(JdkAlpnApplicationProtocolNegotiator.java:122) at io.netty.handler.ssl.JdkSslContext.configureAndWrapEngine(JdkSslContext.java:360) at io.netty.handler.ssl.JdkSslContext.newEngine(JdkSslContext.java:330) at io.netty.handler.ssl.SslContext.newHandler(SslContext.java:953) at io.netty.handler.ssl.SslContext.newHandler(SslContext.java:945) at io.netty.handler.ssl.SniHandler.newSslHandler(SniHandler.java:151) at io.netty.handler.ssl.SniHandler.replaceHandler(SniHandler.java:133) at io.netty.handler.ssl.SniHandler.onLookupComplete(SniHandler.java:114) at io.netty.handler.ssl.AbstractSniHandler.select(AbstractSniHandler.java:275) at io.netty.handler.ssl.AbstractSniHandler.decode(AbstractSniHandler.java:173) at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:498) at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:437)
Hello Ritesh, comments are not meant to resolve issues, for this we have the ticket system which you have already used. Only if you find some incorrect, missing or unclear topic in the article itself you should comment here.
The issue here might be JDK 8 and we need to add a restriction here.