Chapter 7. Resolved Issues
7.1. Resolved Issues
This release of JBoss Data Grid resolves the following issues:
- JDG-2100 and JDG-2097 - JBoss Data Grid Quickstarts Missing Dependencies
-
The
secure-embedded-cacheandcdi-jdgquickstarts fail with errors when you attempt to run them. - JDG-2110 - JBoss Data Grid Eviction Strategy Did Not Take Effect
-
Setting the
Exceptioneviction strategy in the JBoss Data Grid configuration did not take effect. - JDG-2105 - Documentation for the Hot Rod Node.js Client
-
The
Readmedocumentation for Hot Rod Node.js client was not updated to include details on memory profiling capabilities and enhancements to avoid excessive memory consumption. - JDG-2103 - Operations with the Hot Rod Client Took Longer Than Expected after Network Split
- If JBoss Data Grid detected a network split that partitioned nodes, the Hot Rod client took longer than expected to perform operations to the cluster.
- JDG-2071 - Enabling Server Hinting Caused the Management Console to Display Nothing
- If Server Hinting was enabled in the JBoss Data Grid configuration, the Management Console displayed nothing after login.
- JDG-2070 - Failover to Remote Sites Not Successful with Cross-Site Replication
- In an environment where JBoss Data Grid was configured to failover from one site to another, failover did not occur successfully and a warning was thrown.
- JDG-1870 - Hot Rod Node.js Client Had Expired Certificates
- The Hot Rod Node.js client included expired certificates.
- JDG-1053 - The Nodes Tab in the Management Console Returns an HTTP 404 Error
- When opening the Nodes tab for the default cluster, the Management Console returned an HTTP 404 error.
