Red Hat Data Grid 8.5 Release Notes

Data Grid 8.5.5 improves usability, increases performance, and enhances security. Find out what is new.

Data Grid 8.5.5 security update

Data Grid 8.5.5 provides a security enhancement to address CVEs.

For more information see the advisory related to this release RHSA-2025:15612.

Data Grid 8.5.4 improves usability, increases performance, and enhances security. Find out what is new.

Progress logging for long-running tasks

State transfer, Soft Index File Store (SIFS) index rebuild, and query indexing now report progress through periodic log messages. This helps monitor task duration and adjust timeout settings if needed.

Data Grid 8.5.4 security update

Data Grid 8.5.4 provides a security enhancement to address CVEs.

For more information see the advisory related to this release RHSA-2025:10130.

Data Grid 8.5.3 improves usability, increases performance, and enhances security. Find out what is new.

Red Hat Build of Quarkus extensions

The Red Hat Build of Quarkus Embedded extension is now part of the Quarkiverse, along with the Hot Rod Client.

Data Grid 8.5.3 security update

Data Grid 8.5.3 provides a security enhancement to address CVEs.

For more information see the advisory related to this release RHSA-2025:2663.

Data Grid 8.5.2 improves usability, increases performance, and enhances security. Find out what is new.

Simple cache metrics updates

Simple cache mode now provides the same metrics as the other cache modes such as local, distributed, replicated, and invalidation. This simplifies observing cache metrics in observing and alerting systems.

Support for JDBC_PING2 protocol

Data Grid 8.5.2 provides the ability to use JDBC_PING2 protocol for JGroups discovery. It is recommended to use the JDBC_PING2 protocol rather than JDBC_PING protocol with Data Grid 8.5.2.

For more information, see JDBC_PING2.

Data Grid 8.5.2 security update

Data Grid 8.5.2 provides a security enhancement to address CVEs. You must upgrade any Data Grid 8.5.1 deployments to version 8.5.2 as soon as possible.

For more information see the advisory related to this release RHSA-2024:10214.

Data Grid 8.5.1 improves usability, increases performance, and enhances security. Find out what’s new.

Ability to automatically reload SSL/TLS certificates

From Data Grid 8.5.1 onward, when certificates are renewed, Data Grid monitors keystore files for changes and automatically reloads these files, without requiring a server or client restart.

For more information, see SSL/TLS Certificate rotation.

Ability to index keys for indexed remote queries

Data Grid 8.5.1 introduces an Indexed type for keys. You can index the keys in a cache for indexed remote queries by defining these keys as Indexed. This enhancement means that you can index the key fields as well as the value fields, which allows the keys to be used in Ickle queries.

For more information, see Queries by keys.

Data Grid 8.5.0 improves usability, increases performance, and enhances security. Find out what’s new.

Data Grid 8.5.0 security update

Data Grid 8.5.0 provides a security enhancement to address CVEs. You must upgrade any Data Grid 8.4 deployments to version 8.5.0 as soon as possible.

For more information see the advisory related to this release RHSA-2024:4460.

Support for RESP protocol endpoint

The Redis serialization protocol (RESP) protocol endpoint in RHDG, which was provided as a technology preview feature in previous releases, is now fully supported. Additionally, the 8.5 release provides more Redis commands that you can use.

For more information, see Using the RESP protocol endpoint with Data Grid.

getAndSet REST operation for strong counters

This release introduces a new getAndSet REST (Representational State Transfer) operation for strong counters. The getAndSet operation atomically sets values for strong counters with POST requests. If the operation is successful, Data Grid returns the previous value in the payload.

For more information, see Performing getAndSet atomic operations on strong counters.

Aggregate security realm

This release introduces a new security realm called aggregate security realm. You can use an aggregate security realm to combine multiple security realms: one for authentication and the others for authorization.

For more information, see Aggregate security realm.

New Memcached connector

The RHDG 8.5 release replaces the old Memchached connector with a new connector.

The new Memcached connector provides the following improvements:

Thread dump on CacheBackpressureFullException

The most likely cause of CacheBackpressureFullException exception is either hung threads or server overload. Data Grid now creates periodic thread dumps on CacheBackpressureFullException so that you can analyze the cause. By default the interval between two thread dumps is 60 seconds.

Ability to set a stable topology

By default, after a cluster shutdown, Data Grid waits for all nodes to join the cluster and restore the topology. However, you can now mark the current topology stable for a specific cache by using a command by using either CLI or REST.

topology set-stable

topology set-stable

For more information, see Setting a stable Topology.

POST /rest/v2/caches/{cacheName}?action=initialize&force={FORCE}

POST /rest/v2/caches/{cacheName}?action=initialize&force={FORCE}

For more information, see Set a Stable Topology.

Enhancement to ProtoStream logging in MassIndexer

MassIndexer now displays protobuf message name instead of a class name in log message for Protostream objects to improve clarity of the message.

OpenTelemetry Tracing integration

New spans have been introduced to add tracing capabilities to container, persistence, cluster, xsite, and security so that telemetry can be exported to and consumed by OpenTelemetry.

Support for JBoss Marshalling

JBoss Marshalling was deprecated in Data Grid 8.4.6 and earlier versions. It is fully supported in Data Grid 8.5.0.

Data Grid release 8.5.0 removes the following features.

RHDG clients

The following HotRod clients are no longer provided with RHDG:

However, you can continue using older clients with RHDG 8.5.

Java EE dependencies

Support for Java EE dependencies has been removed. All applications added to the RHDG server, and client HotRod applications must be updated to use Jakarta EE dependencies.

JBoss EAP modules

RHDG modules for Red Hat JBoss EAP applications are no longer distributed as a part of the RHDG release.

JBoss EAP users can use the Infinispan subsystem that is integrated within the JBoss EAP product release without the need to separately install RHDG modules. For more information, see EAP 8 now supports full Infinispan functionality, including query, counters, locks, and CDI.

JCache CDI support

RHDG 8.5 removes support for JCache (JSR 107). As an alternative, use other caching API developments in the Jakarta EE ecosystem.

Java 11 support

RHDG 8.5 removes support for Java 11. The minimum supported Java version for RHDG 8.5 is Java 17.

Client HotRod applications that require Java 11 can continue using older versions of client libraries.

Tomcat session manager

Tomcat session manager is not distributed with RHDG 8.5.

RHDG server on Windows

Deploying RHDG server on Windows Server 2019 is no longer supported.

Spring support

Using RHDG with Spring Boot 2.x and Spring 5.x is no longer supported.

Red Hat supports different Java versions, depending on how you install Data Grid.

Removal of Java 11 support

In Data Grid 8.5, support for Java 11 is removed. Users of Data Grid 8.5 must upgrade their applications at least to Java 17.

You can continue using older Hot Rod Java client versions in combination with the latest Data Grid Server version. However, if you continue using older version of the client you will miss fixes and enhancements.

Supported Java versions in Data Grid 8.5

Embedded caches

Red Hat supports Java 17 and Java 21 when using Data Grid for embedded caches in custom applications.

Remote caches

Red Hat supports Java 17 and Java 21 for Data Grid Server installations. For Hot Rod Java clients, Red Hat supports Java 17 and Java 21.

Red Hat supports Java 17 and Java 21 for Data Grid Server, Hot Rod Java clients, and when using Data Grid for embedded caches in custom applications.

Vector database not supported

Vector database features are not supported in Data Grid.

For issues that affect Data Grid clusters that you manage with Data Grid Operator, you should refer to the Data Grid Operator 8.5 release notes.

Description: In bare metal deployments, when JGroups bind to an external IP without authentication configured by default, the connection is not secure, posing a risk of unauthorized access or manipulation.

Workaround: Secure the connection in one of the following ways:

Description: In scenarios where a network partition occurs for a Data Grid cluster, transactions are rolled back after the partition is healed.

Workaround: There is no workaround for this issue.

Description: In some test cases, Data Grid partition handling functionality took longer than expected to perform conflict resolution.

Workaround: There is no workaround for this issue.

See Issues fixed in Red Hat Data Grid 8.5.5 to view the list of issues fixed in this release.

See Issues fixed in Red Hat Data Grid 8.5.4 to view the list of issues fixed in this release.

See Issues fixed in Red Hat Data Grid 8.5.3 to view the list of issues fixed in this release.

See Issues fixed in Red Hat Data Grid 8.5.2 to view the list of issues fixed in this release.

See Issues fixed in Red Hat Data Grid 8.5.1 to view the list of issues fixed in this release.

Data Grid 8.5.0 includes the following notable fixes:

In some cases Data Grid deployments can encounter errors that are caused by the host system or external dependency. This section provides details about any such known issues as well as troubleshooting and workaround procedures.

Nashorn JavaScript engine

If your Data Grid Server uses JavaScript to automate tasks, you must install the Nashorn JavaScript engine to ensure that these scripts can run on Data Grid 8.4. This is because OpenJDK 17 has removed support for the Nashorn JavaScript engine, its APIs, and the jjs tool.

For a bare-metal Data Grid Server, you can install Nashorn from the Maven central repository by issuing the following command in your Data Grid CLI:

bin/cli.sh install org.openjdk.nashorn:nashorn-core:15.4 \
                                 org.ow2.asm:asm:7.3.1 \
                                 org.ow2.asm:asm-util:7.3.1

bin/cli.sh install org.openjdk.nashorn:nashorn-core:15.4 \
                                 org.ow2.asm:asm:7.3.1 \
                                 org.ow2.asm:asm-util:7.3.1

On OpenShift, you can create an Infinispan Custom Resource (CR) that sets the Data Grid Operator to install Nashorn for your Data Grid cluster. For example:

apiVersion: infinispan.org/v1
kind: Infinispan
metadata:
  name: infinispan
spec:
  replicas: 2
  dependencies:
    artifacts:
      - maven: org.openjdk.nashorn:nashorn-core:15.4
      - maven: org.ow2.asm:asm:7.3.1
      - maven: org.ow2.asm:asm-util:7.3.1
  service:
    type: DataGrid

apiVersion: infinispan.org/v1
kind: Infinispan
metadata:
  name: infinispan
spec:
  replicas: 2
  dependencies:
    artifacts:
      - maven: org.openjdk.nashorn:nashorn-core:15.4
      - maven: org.ow2.asm:asm:7.3.1
      - maven: org.ow2.asm:asm-util:7.3.1
  service:
    type: DataGrid