Red Hat Summit Red Hat SummitSupportKonsoleEntwicklerDemo startenKontakt

Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 3. Known and fixed issues

Learn about known issues in Data Grid and find out which issues are fixed.

3.1. Known Issues for Data Grid
Link kopieren

For issues that affect Data Grid clusters running on Red Hat OpenShift, you should refer to the Data Grid Operator 8.2 release notes.

Data Grid Modules for Red Hat JBoss EAP (EAP) are missing dependencies

Issue: JDG-5104

Description: Data Grid Modules for EAP 7.4 do not include all required Hibernate artifacts. Additionally EAP 7.4 removes Eclipse MicroProfile and SmallRye modules that Data Grid requires.

Workaround: Do the following:

  1. Download the Data Grid Server distribution.
  2. Open a terminal window and navigate to the $RHDG_HOME/server/lib directory.

  3. Locate the following Hibernate JAR files:

    • hibernate-search-backend-lucene-6.0.2.Final-redhat-00002.jar
    • hibernate-commons-annotations-5.0.5.Final-redhat-00002.jar

  4. Copy the JAR files to the following directory of your Data Grid Modules installation: 

    modules/system/add-ons/rhdg/org/infinispan/rhdg-8.2/
    Copy to Clipboard Toggle word wrap
  5. Open /modules/system/add-ons/rhdg/org/infinispan/rhdg-8.2/module.xml for editing.

  6. Add the optional="true" attribute to the following modules: 

    <module name="org.eclipse.microprofile.config.api" export="true" optional="true"/>
<module name="org.eclipse.microprofile.metrics.api" export="true" optional="true"/>
<module name="io.smallrye.config" services="export" export="true" optional="true"/>
<module name="io.smallrye.metrics" services="import" export="true" optional="true"/>
    Copy to Clipboard Toggle word wrap

Deadlock occurs when putAll() operations write to expired entries with optimistic locking

Issue: JDG-5087

Description: With transactional caches that use optimistic locking, commands to remove expired entries acquire locks even when the expiration was triggered by a write operation. In some cases, when putAll() operations write to expired entries, this behavior can lead to deadlocks.

Workaround: There is no workaround for this issue.

Data race occurs when handling expired entries with putAll() or getAll() operations

Issue: JDG-5028

Description: When a putAll() or getAll() operation affects two or more entries, both those entries can expire. If the keys for both entries map to the same HashMap bucket then one of the updates can be lost and Data Grid throws the following exception: 

IllegalStateException: Entry should be always wrapped!
Copy to Clipboard Toggle word wrap

Workaround: There is no workaround for this issue.

Clients cannot connect to remote caches that use TLS/SSL encryption

Issue: JDG-4763

Description: Clients cannot connect to remote caches and Data Grid logs print a WARN log message related to TLS/SSL.

This issue originates from the WildFly OpenSSL library that is included in Data Grid. See the following Red Hat knowledge base article for full details about log messages: Clients are not able to connect a server after update to RHDG 8.2.1

Workaround: Start Data Grid Server with the following property to use Java TLS/SSL libraries instead of OpenSSL: 

-Dorg.infinispan.openssl=false
Copy to Clipboard Toggle word wrap

Session externalization from Red Hat JBoss Web Server to Data Grid 8.2 is available with 7.3.8 or 8.1.1 versions of the Tomcat session client

Issue: JDG-4599

Description: Data Grid 8.2 does not yet include the Tomcat session client, which will be available after EAP 7.4 GA.

Workaround: Use Data Grid Server 8.2 in combination with a Data Grid 7.3.8 or 8.1.1 version of the Tomcat session client with the following configuration: 

<Manager className="org.wildfly.clustering.tomcat.hotrod.HotRodManager"
         configurationName="default"
         persistenceStrategy="${persistenceStrategy}"
         server_list="127.0.0.1:11222"
         protocol_version="2.9"
         auth_realm="default"
         sasl_mechanism="DIGEST-MD5"
         auth_server_name="infinispan"
         auth_username="admin"
         auth_password="changeme"/>
Copy to Clipboard Toggle word wrap

Hot Rod clients using Java 8 need upgrade to avoid SSLHandshakeException

Issue: JDG-4279

Description: Using JDK 8 with Hot Rod clients results in the following fatal exception if your Java version is not 8u252 at a minimum: 

SSLHandshakeException: Remote host closed connection during handshake at sun.security.ssl.SSLSocketImpl
Copy to Clipboard Toggle word wrap

Workaround: Ensure you are using Java 8u252 at a minimum. This version includes required security features for Application-Layer Protocol Negotiation (ALPN).

Data Grid Conflict Resolution Performance

Issue: JDG-3636

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.

Data Grid Does Not Passivate JWS Sessions Correctly

Issue: JDG-2796

Description: When externalizing sessions from JBoss Web Server (JWS), sessions are not passivated correctly if using the FINE persistence strategy.

Workaround: There is no workaround for this issue.

3.2. Fixed in Data Grid 8.2.0
Link kopieren

Data Grid 8.2.0 includes the following notable fixes:

  • JDG-4315 IllegalArgumentException when performing rolling upgrades with transactional caches.
  • JDG-3972 Inconsistent query behavior when indexed caches contain non-indexed Protobuf entities.
  • JDG-4520 DB2TableManager looks into all schemas during table existence check.
  • JDG-4425 JGroups retransmission requests are too frequent and too large.
  • JDG-4420 ClassNotFoundException happens when putting a custom object with jboss-marshalling on EAP embedded module.
  • JDG-4387 Simple cache with statistics enabled results in NullPointerException in EvictionManagerImpl.
  • JDG-4375 How to disable TLS 1.1 and enable only TLS 1.2.
  • JDG-4370 Make AWS dependencies optional in EAP modules.
  • JDG-4351 Slow performance can happen and can face a transaction timeout due to the cost of invoking Arrays.fill(keys, null) against a huge array on IdentityIntMap#clear().
  • JDG-4344 Experiencing a memory leak on the HotRod client when we put entries with a big value size.
  • JDG-4339 Conflict resolution fails in transactional cache.
  • JDG-4315 IllegalArgumentException when doing Rolling Upgrades on transactional caches.
  • JDG-4281 Infinispan operator CR not accepting changes in logging level.
  • JDG-4152 Infinispan CR not idempotent when removing "expose" configuration.

3.3. Fixed in Data Grid 8.2.1
Link kopieren

Data Grid 8.2.1 includes the following notable fixes:

  • JDG-4678 Upgrading to Data Grid 8.2 from 8.1 fails and data is corrupted if caches persist data to Single File cache stores.
  • JDG-4713 Global state incompatibility.
  • JDG-4649 Thread contention when retrieving the cache via CacheContainer.getCache(String cacheName).
  • JDG-4590 UnsupportedOperationException when querying caches with JSON data types.
  • JDG-4563 Implicit cache lock release failure.
  • JDG-4438 Concurrent modifications succeed in pessimistic caches.
  • JDG-4414 Delete one of two pods then scale down to one seems to corrupt the cluster state.
  • JDG-3970 Throttle TLS handshake failed NotSslRecordException WARN message.

3.4. Fixed in Data Grid 8.2.2
Link kopieren

Data Grid 8.2.2 includes the following notable fixes:

  • JDG-5036 Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value.
  • JDG-4947 Cross-site replication tombstone leaks.
  • JDG-4984 Logging of WrappedByteArray includes entire values and unnecessarily increases the size of log files.
  • JDG-5043 ResultSets are not closed when using JDBC cache stores in some cases, resulting in log file warnings.

3.5. Fixed in Data Grid 8.2.3
Link kopieren

Data Grid 8.2.3 includes the following notable fixes:

  • JDG-5060 Denial of Service (DoS) in Log4j 2.x with thread context message pattern and context lookup pattern.
  • JDG-5068 Remote code execution in Log4j 2.x via JDBC Appender.
  • JDG-5066 Denial of Service (DoS) in Log4j 2.x with Thread Context Map (MDC) input data contains a recursive lookup and context lookup pattern.

3.6. Host system and dependency issues
Link kopieren

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.

TLS on Red Hat Enterprise Linux 7

RHEL 7 provides a version of the OpenSSL library that does not yet offer support for TLSv1.3. However Data Grid Server 8.2 enables TLSv1.3 and TLSv1.2 by default, which causes errors with client connections for encrypted Hot Rod and REST endpoints.

Data Grid Server also logs messages such as the following: 

WARN  [org.infinispan.HOTROD] ISPN004098: Closing connection due to transport error
org.infinispan.client.hotrod.exceptions.TransportException:: ISPN004077:
Closing channel due to error in unknown operation.
Copy to Clipboard Toggle word wrap

If you install Data Grid Server on RHEL 7 you should use the native Java SSL library by disabling OpenSSL with the following JVM option: 

-Dorg.infinispan.openssl=false
Copy to Clipboard Toggle word wrap
Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat