6.2. Resolved Issues

In Red Hat JBoss Data Grid, when both infinispan-remote and infinispan-embedded dependencies are on the classpath, the Infinispan CDI extension does not work as expected. This is due to bundling the Infinispan CDI extension in both jar files. As a result, CDI fails with ambiguous dependencies exception.

This is resolved as of Red Hat JBoss Data Grid 6.6.0. The content of infinispan-embedded and infinispan-remote were restructured so that only one of the jar files is needed for any use case. There is no need to use them together anymore.

The server configuration did not allow users to specify write skew check option. This behavior could lead to inconsistencies on failure scenarios when using conditional operations with optimistic locking caches.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0, where write skew check is automatically enabled when using a combination of optimistic locking, synchronous cache mode, and REPEATABLE_READ isolation level.

The metrics for local caches were not properly registered within the server. As a result, local cache resources were not available in the JON UI. This issue was only related to local caches and did not affect clustered caches.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0.

In Red Hat JBoss Data Grid the custom audit logger option was ignored in server mode, and the default audit logger was not turned on.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0. Users can now set up their own audit logger, and if no audit logger is provided, then the default audit logger is used.

When using a cache configured with expiration in remote JCache implementation, expiration events were not handled in clustered environment on cache c1, if the insertion of an entry was performed by cache c2. As a consequence, cache entry listener registered on cache c1 was not notified of the expiration event.

The issue is resolved as of Red Hat JBoss Data Grid 6.6.0, and cache entry listeners receive expiration events correctly in clustered environment.

When using the HotRod client in JBoss Data Grid's Remote Client-Server mode, there was a possibility that an outdated view was used when the cluster healed from network partition. This could lead to data inconsistencies when performing operations by clients that received different views.

The issue is resolved as of Red Hat JBoss Data Grid 6.6.0. The HotRod client correctly receives an updated view after the partition is healed.

In Red Hat JBoss Data Grid, when roles based authentication was enabled, the HotRod client did not fail over; instead, it logged the exception when the JDG server to which the client was connected and went offline.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0. If the JDG server shuts down, then the HotRod client will fail over to another JDG server in the cluster silently, with no exception logged and the HotRod client will continue to work properly.

Expiration settings of a cache were ignored in JBoss Data Grid server if putIfAbsent operation was invoked via HotRod client. This could lead to wrong assumptions about presence of an entry in the cache, which never expired.

The issue is resolved as of Red Hat JBoss Data Grid 6.6.0. The entry correctly expires after predefined time period.

In Red Hat JBoss Data Grid, when node authentication was enabled and a JDG node left the cluster it was not able to rejoin the cluster.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0. When node authentication is turned on, then the JDG node can rejoin the cluster without any issue.

When size() is performed using the HotRod client, a MapReduce task is invoked internally to determine the total number of entries present in the cache. Previously this operation did not require any permissions; however, a check has been added to ensure the role invoking size() has the BULK_READ permission.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0.

There was a possibility of a transactional cache erroneously throwing ClassCastException when an entry was obtained while located on a remote node.

This issue is resolved as of Red Hat JBoss Data Grid 6.6.0.