Chapter 2. Known and fixed issues

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

2.1. Known Issues for 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.3 release notes.

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.

Inconsistent transactions when network partitions occur

Issue: JDG-3935

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.

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

Issue: JDG-4599

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

Workaround: Use Data Grid Server 8.3 in combination with the Data Grid 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"/>

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 Server cannot use some credential keystores

Issue: JDG-4711

Description: In some cases, Data Grid Server logs the following exceptions when using credential keystores: 

java.lang.RuntimeException: org.wildfly.security.credential.store.CredentialStoreException: ELY09508: Cannot write credential to store
...
Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09508: Cannot write credential to store
...
Caused by: java.security.KeyStoreException: Cannot store non-PrivateKeys

In most cases, this error indicates that a JKS keystore contains symmetric keys instead of public and private keys.

Workaround: Ensure that the credential keystore uses asymmetric keys.

2.2. Fixed in Data Grid 8.3.0

Data Grid 8.3.0 includes the following notable fixes:

  • JDG-4947 Asynchronous cross-site replication results in tombstone leaks
  • JDG-5028 Data race occurs when handling expired entries with putAll() or getAll() operations
  • JDG-4763 Clients cannot connect to remote caches that use TLS/SSL encryption
  • JDG-4797 Hot Rod client manual cluster switch not working
  • JDG-4860 Hot Rod Java client retries operations too many times
  • JDG-3629 Maximum idle expiration does not work with eviction and cache stores configured with passivation
  • JDG-3916 Data Grid Console logs incomplete messages when turning sites on or off
  • JDG-4530 Cross-site replication automatic state transfer with empty exception using set state mode
  • JDG-4598 Data Grid Console prompts users to select a cache template when cache configuration is not valid
  • JDG-4852 Data Grid Server running as a Microsoft Windows service does not shutdown if Hot Rod clients are connected

2.3. Fixed in Data Grid 8.3.1

Data Grid 8.3.1 includes the following notable fixes:

  • JDG-2796 Data Grid does not passivate JWS sessions correctly
  • JDG-4092 Cache persistent state is not deleted after successful cluster restart
  • JDG-5220 Ickle fulltext query not working with query parameters
  • JDG-5097 Backups fail when a Protobuf schema key contains forward slashes
  • JDG-5076 RemoveExpiredCommand does not remove entries on backup if equals is not implemented
  • JDG-5104 Data Grid Modules for Red Hat JBoss EAP (EAP) are missing dependencies
  • JDG-4657 Hot Rod client fails to connect when there is no bind address argument and servers are not on the same subnet
  • JDG-5245 ClassCastException with Oracle string-keyed-jdbc-store
  • JDG-5161 Compactor fails when removing content from persistent storage

2.4. Host system and dependency issues

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.3 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.

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

Additional resources