Data Grid 7.3.11 provides a security enhancement to address CVEs. You must upgrade any Data Grid 7.3 deployments to version 7.3.11 as soon as possible. For more information see the advisory related to this release RHSA-2023:6286.

Red Hat recommends you upgrade any deployments from 7.3.x to the latest Data Grid 8 version as soon as possible. The Data Grid team regularly patch security vulnerabilities and actively fix issues on the latest version of the software.

Find the latest Data Grid documentation at: Data Grid product documentation

For more information about Data Grid version lifecycle and support details, see Data Grid Product Update and Support Policy

Data Grid 7.3.10 provides a security enhancement to address a CVE. You must upgrade any Data Grid 7.3 deployments to version 7.3.10 as soon as possible. For more information see the advisory related to this release RHSA-2023:1303.

Red Hat recommends you upgrade any deployments from 7.3.x to the latest Data Grid 8 version as soon as possible. The Data Grid team regularly patch security vulnerabilities and actively fix issues on the latest version of the software.

Find the latest Data Grid documentation at: Data Grid product documentation

For more information about Data Grid version lifecycle and support details, see Data Grid Product Update and Support Policy

Data Grid 7.3.9 removes Log4j version 1.x components to address a critical security vulnerability as well as other CVEs of moderate severity. You must upgrade any Data Grid 7.3 deployments to version 7.3.9 as soon as possible.

Any custom components that rely on Log4j version 1.x capabilities, such as a cache loader or a server task implementation, no longer work because Data Grid 7.3.9 does not ship with Log4j version 1.x.

Red Hat recommends you upgrade any deployments from 7.3.x to the latest Data Grid 8 version as soon as possible. The Data Grid team regularly patch security vulnerabilities and actively fix issues on the latest version of the software.

Find the latest Data Grid documentation at: Data Grid product documentation

For more information about Data Grid version lifecycle and support details, see Data Grid Product Update and Support Policy

Data Grid Server is upgraded to EAP 7.3.10, which provides performance improvements and includes several CVE fixes to enhance security.

Data Grid 7.3.9 upgrades JBoss marshalling to version 2.0.12.Final.

Data Grid Server is upgraded to EAP 7.3.4, which provides performance improvements and includes several CVE fixes to enhance security.

Data Grid Server is upgraded to EAP 7.2.9, which provides performance improvements and includes several CVE fixes to enhance security.

When performing rolling upgrades of Data Grid clusters, target clusters more efficiently retrieve data from source clusters.

Data Grid server is upgraded to EAP 7.2.7, which provides performance improvements and includes several CVE fixes to enhance security.

This release of Data Grid upgrades to Spring versions as follows:

The Red Hat Data Grid Command-Line Interface (CLI) provides the following commands to start and stop Red Hat Data Grid endpoint connectors:

See Starting and Stopping Red Hat Data Grid Endpoints for more information.

When executing tasks on Red Hat Data Grid servers via remote Hot Rod clients, task names are now included in the Hot Rod access logs.

See Access Logs for more information about Hot Rod access logs.

This release includes several improvements to cross-site replication performance. Red Hat Data Grid now:

Clustered max-idle expiration is enhanced in this release to prevent data loss with clustered cache modes.

As of this release, when clients read entries that have max-idle expiration values, Red Hat Data Grid sends touch commands to all owners. This ensures that the entries have the same relative access time across the cluster.

See Maximum Idle Expiration.

As of this release, when Hot Rod client connections time out, Red Hat Data Grid provide additional detail about connections in exception messages, as in the following example:

org.infinispan.client.hotrod.exceptions.TransportException::
java.net.SocketTimeoutException: ContainsKeyOperation{ExpirationCache,
key=[B0x033E0131, flags=0} timed out after 60000 ms

org.infinispan.client.hotrod.exceptions.TransportException::
java.net.SocketTimeoutException: ContainsKeyOperation{ExpirationCache,
key=[B0x033E0131, flags=0, connection=127.0.0.1/127.0.0.1:11222} timed out
after 60000 ms

As of this release, Data Grid Hot Rod C++ clients allow you to configure the recover policy when the connection pool is exhausted.

Data Grid server documentation was updated to describe how to collect JMX statistics with Prometheus.

See Exposing JMX Beans to Prometheus.

The Data Grid User Guide was updated to clarify capacity factor configuration for cross-site replication.

See "Capacity Factors" in Key Ownership.

Data Grid server is upgraded to EAP 7.2.5, which provides performance improvements and includes several CVE fixes to enhance security.

This release of Data Grid upgrades to Spring Boot 2.2.0, which uses Spring 5 dependencies as follows:

Data Grid expires entries from clustered caches only when the primary owners determines the entries meet the expiration criteria. This change improves performance by reducing duplicate expiration commands.

When expiring entries, Red Hat Data Grid replicates a command that removes expired entries across clusters. As of this release Red Hat Data Grid no longer replicates this command across sites, which improves performance.

Documentation is added to note the fact that CLI sessions expire after an idle timeout of six minutes. See the Command-Line Interface (CLI) section for more information.

Data Grid server is upgraded to EAP 7.2.4, which provides performance improvements and includes several CVE fixes to enhance security.

Changes to the AWS S3 API require Data Grid to use NATIVE_S3_PING instead of the JGroups S3_PING protocol.

JGroups S3_PING no longer works for server discovery on AWS. You should migrate any existing S3_PING configurations to NATIVE_S3_PING.

For more information, see the following:

This release includes changes that improve transport layer performance for Data Grid clusters in Library Mode:

The Data Grid REST endpoint now allows access to caches that are configured for authorization.

This enhancement resolves the issues outlined in this KCS Solution.

The protostream library component in Data Grid is updated to 4.2.4.Final.

Data Grid now applies the take-offline configuration when using Cross-Site Replication capabilities with asynchronous replication strategies.

Data Grid adds the following statistics for asynchronous cross-site replication:

See the JMX Components documentation for more information.

Core module dependencies for Data Grid 7.3.2 in Server Mode align with EAP 7.2.1.

The Hot Rod client now includes a SKIP_LISTENER_NOTIFICATION flag so that client listeners do not get notified by the Data Grid server when session IDs change.

This flag resolves issues when using spring-session integration with Spring 5. If you are using spring-session with Spring 5, you should upgrade both the Data Grid server and Hot Rod client to 7.3.2.

Likewise, you must upgrade both the Data Grid server and Hot Rod client to 7.3.2 or later before you can set the SKIP_LISTENER_NOTIFICATION flag.

For more information, see Skipping Notifications in the Data Grid User Guide.

Data Grid now supports Java 11. See the supported configurations at https://access.redhat.com/articles/2435931.

Data Grid now supports OpenJDK 8 on Windows. See the supported configurations at https://access.redhat.com/articles/2435931.

Data Grid now uses JGroups version 4.0.18.Final. See the component details at https://access.redhat.com/articles/488833.

Data Grid can now use the JGroups DNS_PING protocol for cluster discovery.

For more information, see JGroups Subsystem Configuration.

This release adds the LOGGING_CATEGORIES environment variable that adjusts the categories and levels for which Data Grid captures log messages. See Monitoring and Logging for more information.

Data Grid now provides a default filename analyzer. For more information, see Default Analyzers.

This release includes several improvements for Data Grid for OpenShift, including:

Visit the Data Grid for OpenShift Documentation to find out more and get started.

This release of Data Grid improves integration with well-known enterprise Java frameworks such as Spring and Hibernate.

public void put(Object key, Object value, long lifespan, TimeUnit unit) {
      this.cacheImplementation.put(key, value != null ? value : NullValue.NULL, lifespan, unit);
}

public void put(final Object key, final Object value) {
      this.nativeCache.put(key, value);
      try {
         if (writeTimeout > 0)
            this.nativeCache.putAsync(key, value != null ? value : NullValue.NULL).get(writeTimeout, TimeUnit.MILLISECONDS);
         else
            this.nativeCache.put(key, value != null ? value : NullValue.NULL);
      } catch (InterruptedException e) {
         Thread.currentThread().interrupt();
         throw new CacheException(e);
      } catch (ExecutionException | TimeoutException e) {
         throw new CacheException(e);
      }
   }

Data Grid provides transcoding capabilities that convert data between formats that is suitable for different endpoints. For example, you can write ProtoBuf-encoded data through the Hot Rod endpoint and then retrieve it as a JSON document through the REST endpoint.

Data Grid includes a set of default analyzers that convert input data into one or more terms that you can index and query.

For more information, see Analysis.

This release exposes new operations and metrics through JMX:

For more information, see jmxComponents.

The invokeAll() method in the LockedStream interface now provides a way to execute code for entries where locks are held for the respective keys, allowing you to not have to acquire locks and be able to guarantee the state for values.

For more information, see org.infinispan.LockedStream.

The AdvancedCache interface now includes a withSubject() method that performs operations with the specified subject when authorization is enabled on caches.

See the Javadocs for the AdvancedCache interface.

Data Grid now provides support for HTTP/2 with the REST endpoint.

Red Hat Data Grid for OpenShift gives you cross-site replication capabilities to backup data across clusters in running different data centers.

C++ and C# Hot Rod clients now offer an implementation of the RemoteCacheManagerAdmin interface that lets you perform administrative operations remotely.

C++ and C# Hot Rod clients now provide capabilities for remotely working with clustered counters.

The Data Grid administration console now lets you configure and manage endpoint configuration and provides the following capabilities for manipulating data:

Additionally, the administration console includes a basic protobuf schema editor.

Red Hat Data Grid 7.3.9 includes the following notable fixes:

Red Hat Data Grid 7.3.8 includes the following notable fix:

Red Hat Data Grid 7.3.7 includes the following notable fixes:

Red Hat Data Grid 7.3.6 includes the following notable fixes:

Red Hat Data Grid 7.3.5 includes the following notable fixes:

Red Hat Data Grid 7.3.4 includes the following notable fixes:

Red Hat Data Grid 7.3.3 includes the following notable fixes:

Red Hat Data Grid 7.3.2 includes the following notable fixes:

Red Hat Data Grid 7.3.1 includes the following notable fixes:

The Data Grid server is based on EAP 7.2 in this release. Make sure you consult the right version of the EAP documentation and that any underlying EAP configuration or setup is supported in 7.2.

For information about supported versions of EAP in this release, see the supported configurations at https://access.redhat.com/articles/2435931.

Data Grid now provides Library and Java Hot Rod Client modules for EAP as a single package. In previous releases, Data Grid provided Library modules and Java Hot Rod Client modules as separate packages. Download the modules for EAP from the customer portal.

For Apache Camel integration, the Red Hat Fuse team actively develop and maintain a camel-infinispan component that supersedes the camel-jbossdatagrid component. Red Hat recommends that you use the camel-infinispan component that is available with Red Hat Fuse 7.3 and later.

Refer to Red Hat Fuse documentation for more information.

Data Grid 7.3 introduces changes to internal marshalling functionality that are not backwardly compatible with previous versions of Data Grid. As a result, Data Grid 7.3.x and later cannot read cache stores created in earlier versions of Data Grid. Additionally, Data Grid no longer provides some store implementations such as JDBC Mixed and Binary stores.

Use StoreMigrator.java to migrate cache stores. This migration tool reads data from cache stores in previous versions and rewrites the content for compatibility with the current marshalling implementation.

For more information, see Store Migrator.

The Data Grid Memcached endpoint no longer stores keys as java.lang.String. For better compatibility Data Grid stores keys as byte[] arrays that represent UTF-8 encoded strings.

If you use the Memcached endpoint, you should reload data in the cache to store keys as byte[]. Either perform a rolling upgrade or load the data from an external source.

The default memcache-connector is disabled for security considerations. To enable the memcache-connector you must configure the endpoint subsystem. See Memcached Connector Configuration.

Distributed scripts with a text-based data type no longer return null when the result from each server is null. The response is now a JSON array with each individual result, for example: [null, null].

The threads that handle the child Netty event loops have been renamed from *-ServerWorker to *-ServerIO.

You cannot configure cache stores as shared and then enable passivation for the stores. This configuration can result in data inconsistencies because it is not possible to synchronize data across nodes. For this reason, Data Grid now throws an exception at startup if it detects this configuration.

The default number of shards is now 4. In previous releases, the default number of shards was equal to the number of segments in the cache.

The AdvancedCacheLoader SPI allows Reactive Streams-based publishKeys and publishEntries methods that improve performance, threading, and ease of use. This change affects custom CacheLoader implementations.

This release deprecates features and functionality that affect migration to Data Grid 7.3. Notably compatibility mode is deprecated by configuring the MediaType for key/value pairs and storing data in binary format. The LevelDB cache store is also deprecated and replaced with the RocksDB.

For the complete list, see Features and Functionality Deprecated in Data Grid 7.3.