Chapter 4. Known and Fixed Issues

Issue: JDG-3826

Description: With Data Grid server deployments, if you set the path of the global persistent location relative to the infinispan.server.data.path property, Data Grid does not set that path in the configuration and the following exception is written to the server log file:

org.infinispan.commons.CacheConfigurationException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,130]
Message: Missing required property '/user/path/to/server/data' for attribute 'relative-to'

Workaround: Set the path in the global persistent location instead of using the property, for example:

<global-state>
  <persistent-location path="tmp/example" relative-to=/user/path/to/server/data"/>
</global-state>

Issue: JDG-1492

Description: When running functional tests for the JDBC String-Based cache store with Sybase databases, cache stores become unresponsive and the functional tests fail. This issue occurs because Sybase databases do not support batch updates to binary columns.

Workaround: Set a value of true for the property infinispan.jdbc.upsert.disabled on the JDBC String-Based cache store. This property executes write operations individually instead of in batches.

Issue: JDG-3643

Description: The default network service that Data Grid Operator creates for Data Grid clusters on OpenShift is missing a port name. As a result, the Prometheus console attempts to collect Data Grid metrics from the 8888/metrics target as well as 11222/metrics.

Workaround: There is no workaround for this issue.

Issue: JDG-3591

Description: Data Grid Operator does not automatically encrypt Data Grid endpoints with OpenShift service certificates.

Workaround: Set the spec.security.endpointEncryption configuration in your Infinispan CR. See Securing Data Grid Connections.

Issue: JDG-3494

Description: If cache names contain the "/" character, it is not possible to access them remotely via the CLI or REST API.

Workaround: There is no workaround for this issue.

Issue: HRJS-88

Description: The Hot Rod JS client behaves unexpectedly and the following exceptions are logged when using encrypted connections to Data Grid server:

[org.infinispan.server.hotrod.HotRodHeader] ISPN006010: Conditional operation
'FOO' should be used with transactional caches, otherwise data inconsistency
issues could arise under failure situations

[org.infinispan.server.hotrod.HotRodHeader] ISPN006011: Operation 'FOO' forced
to return previous value should be used on transactional caches, otherwise data
inconsistency issues could arise under failure situations

[org.infinispan.SECURITY] ISPN000946: Using OpenSSL Provider ...

Workaround: There is no workaround for this issue.

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.

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.

Issue: JDG-3504

Description: JBoss Enterprise Application Platform (EAP) throws the following exception if remote cache store configurations pre-load data into memory:

ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.web.jws-session-dist-async.war: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.web.jws-session-dist-async.war: org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PreloadManager.start() on object of type PreloadManager

Workaround: Ensure that the remote cache store configuration uses preload="false".

Issue: JDG-3624

Description: It is possible to perform operations to access data and control Data Grid nodes with unauthenticated requests from both REST and Hot Rod endpoints.

Workaround: Configure endpoint authentication before you start Data Grid server instances. See Configuring Endpoint Authentication Mechanisms for more information.

Issue: JDG-3558

Description: Data Grid has tested using JDBC drivers, ojdbc10.jar, with JDK 11 to create persistent cache stores with Oracle 19c database. Test results indicate that Oracle Database 19c JDBC drivers are not compatible with JDK 11.

Workaround: Use ojdbc8.jar with JDK 8.

Issue: JDG-3552

Description: NoClassDefFoundError: sun/reflect/ReflectionFactory exceptions occur if you package the Data Grid Hot Rod Java client as a WAR file in an JBoss Enterprise Application Platform (EAP) deployment and use JBoss Marshalling.

Workaround: Include WEB-INF/jboss-deployment-structure.xml in your WAR file as follows:

<jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.1">
  <deployment>
    <dependencies>
      <system export="true">
        <paths>
          <path name="sun/reflect"/>
        </paths>
      </system>
    </dependencies>
  </deployment>
</jboss-deployment-structure>