Chapter 17. Known Issues for Data Grid 7.3

Issue: JDG-4224

Description: The following exception is thrown when using the Hot Rod Java client on Java 8 with GSSAPI security mechanisms:

org.infinispan.client.hotrod.exceptions.HotRodClientException: javax.security.sasl.SaslException: ELY05123: No security layer selected but message length received

This issue occurs due to stricter requirements for Kerberos authentication with the Elytron subsystem in EAP 7.3.

Workaround: Add the wildfly.sasl.relax-compliance property to the sasl security realm in your Data Grid Server configuration:

<authentication security-realm="ApplicationRealm">
  <sasl server-context-name="hotrod-service" server-name="node0" mechanisms="GSSAPI" qop="auth" strength="high medium low">
    <policy>
      <no-anonymous value="true" />
    </policy>
    <property name="wildfly.sasl.relax-compliance">true</property>
  </sasl>
</authentication>

Issue: JDG-3965

Description: If you attempt to store data as unmarshalled, Plain Old Java Objects (POJO) on Data Grid Server, and then read and write data in JSON format, the following exception occurs:

com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Illegal type (com.example.MyClass) to deserialize: prevented for security reasons

Workaround: Specify user classes with the following system property with Data Grid Server:

-Djackson.deserialization.whitelist.packages=com.example

Specify fully qualified class names as follows:

-Djackson.deserialization.whitelist.packages=com.example.MyClass

Issue: JDG-4024

Description: The Data Grid ConfigMap quickstart, _Customizing Data Grid Service Deployments, does not work as expected for versions 7.3.4, 7.3.5, and 7.3.6.

Data Grid for OpenShift 7.3.4 and later uses an updated logging formatter which is not compatible with the logging formatter in the ConfigMap quickstart. As a result it is not possible to start customized Data Grid server images with the quickstart.

Workaround: Use the 7.3.7 tags for the quickstart or work with the 7.3.x branch.

Issue: JDG-3376

Description: The Data Grid for OpenShift image for OpenShift Container Platform on IBM Z or IBM Power does not provide drivers for MySQL and PostgreSQL cache stores.

Workaround: There is no workaround for this issue.

Issue: JDG-3395

Description: Data Grid for OpenShift for OpenShift Container Platform on IBM Z or IBM Power contains Liveness probe failed: and Readiness probe failed: error messages.

Workaround: Ignore the error messages. They stop after the image is ready.

Issue: JDG-3348

Description: If you stop a controller node in a Data Grid cluster configured for cross-site replication and then run the site command with the Data Grid CLI, the following exception occurs:

org.infinispan.remoting.responses.CacheNotFoundResponse cannot be cast to org.infinispan.remoting.responses.SuccessfulResponse

Workaround: Wait until the Data Grid node is completely removed from the cluster view before running the site command.

Issue: JDG-2758

Description: Data Grid 7.3 certification with Red Hat Fuse 6 not possible due to test failures.

Workaround: There is no workaround for this issue.

Issue: JDG-2800

Description: Red Hat Fuse 6 and 7 are not compatible with Java 11. As a result, you cannot use Data Grid 7.3 with Red Hat Fuse 6 and 7 in conjunction with Java 11.

Workaround: There is no workaround for this issue.

Issue: JDG-2871

Description: Running Data Grid with EAP 6 and MySQL 5 can result in unexpected behavior.

Workaround: There is no workaround for this issue.

Issue: JDG-2559

Description: Data Grid 7.3 libraries do not deploy successfully on EAP 6 or Oracle WebLogic.

Workaround: There is no workaround for this issue.

Issue: JDG-2832

Description: Attempting to perform a rolling upgrade from Data Grid 6.6.2 to Data Grid 7.3 results in exceptions and data does not migrate successfully.

Workaround: There is no workaround for this issue.

Issue: JDG-2796

Description: Setting the persistenceStrategy attribute to a value of FINE causes HTTP session externalization to behave unexpectedly.

Workaround: Set the persistenceStrategy attribute to a value of COARSE.

Issue: JDG-2761

Description: It is not currently possible to use a RocksDB Cache Store on Red Hat Enterprise Linux 6 or Microsoft Windows platforms.

Workaround: There is no workaround for this issue.

Issue: JDG-2546

Description: The following error was encountered when creating a RocksDB cache store on RHEL 6: /lib64/libc.so.6: version `GLIBC_2.14' not found.

Workaround: There is no workaround for this issue.

Issue: JDG-1424

Description: In Remote Client-Server mode, if you set the SKIP_CACHE_LOAD flag in the cache store configuration and enable authentication on Hot Rod clients, all entries are retrieved from the cache, including evicted entries.

Workaround: There is no workaround for this issue.

Issue: JDG-1843

Description: Actions available for the Data Grid cluster are not available in the Administration Console if you choose to restart the cluster after changing the configuration. In this case, the cluster is in the Reload-Required state.

Reload and Stop actions are available for each node in the cluster.

Workaround: Reload at least one node in the cluster to restore actions at the cluster level.

Issue: JDG-1804

Description: If Data Grid is running in domain mode and you change the eviction strategy in the configuration through the Administration Console but do not restart to apply the changes, an error occurs.

Workaround: Restart the server after changing to the eviction strategy.

Issue: JDG-991

Description: When performing a rolling upgrade of Data Grid, all migrated data can be deleted from the target cluster after the nodes in the source cluster are taken offline.

Workaround: There is no workaround for this issue.

Issue: JDG-968

Description: If you store data in a cache store with Data Grid 7.0 and earlier and then attempt to read that data with Data Grid 7.1 or later, an error occurs and it is not possible to read the data.

Workaround: There is no workaround for this issue.