Chapter 5. Known and Resolved Issues

When creating a new template the JDBC cache store configuration is not copied over, and must instead be manually entered.

This is a known issue in JBoss Data Grid 7.0.1, and no workaround exists at this time.

When executing the JMX operation ClusterCacheStats.resetStatistics() none of the cluster statistics are reset.

This is a known issue in JBoss Data Grid 7.0.1, and to workaround this issue execute Statistics.resetStatistics() on each server individually.

When executing container or cache based commands through the CLI in domain mode the following message is displayed:

Container does not exists

This is a known issue in JBoss Data Grid 7.0.1, and no workaround exists at this time.

Unlike the C++ and Java Hot Rod clients, the C# client does not include asynchronous versions of cache operations at this time.

This is a known issue in JBoss Data Grid 7.0.1, and a workaround exists by using the Task API to wrap the cache operation. For instance, the following example demonstrates performing an asynchronous Put(key, value):

await Task.Run(() => cache.Put(k,v))

When attempting to insert values into a cache using the Spark connector while compatibility mode is enabled the request will fail with a ClassCastException.

This is a known issue in JBoss Data Grid 7.0.1, and to workaround this issue disable compatibility mode.

It is not possible to use scripts that create a Stream in JavaScript when the cluster is in DIST mode. Any attempts to execute these scripts will result in a NotSerializableException, as the lambdas fail when attempting to be serialized.

This is a known issue in JBoss Data Grid 7.0.1, and to workaround this issue it is recommended to manually iterator over data using an Iterator, or to execute lambdas after the data has been transferred from the script to the originator node.

When using CDI annotations with the CDI 1.1 API, such as the version found within JBoss EAP 7, a java.lang.RuntimeException is thrown; this exception is thrown as the cache events used by JBoss Data Grid 7.0 include content that has been removed by CDI 1.1.

This is a known issue in JBoss Data Grid 7.0.1. This issue is resolved in the CDI 1.2 API; to workaround this issue attach the listeners manually, as outlined in the following steps:

When updating one server group's transport configuration through the Administration Console and accepting the prompt to restart the server group remains running. Instead, a second server group is restarted in its place.

This is a known issue in JBoss Data Grid 7.0.1, and no workaround exists at this time.

When attempting to use the JGroups ENCRYPT protocol a ArrayIndexOutOfBoundsException is thrown.

This is a known issue in JBoss Data Grid 7.0.1, and to workaround this issue use the SYM_ENCRYPT or ASYM_ENCRYPT protocols, as described in the JBoss Data Grid Administration and Configuration Guide.

Cross-Site replication with multiple site masters may not work properly when configured asynchronously.

Data can be stored inconsistently because the replication relies on the delivery order of the updates to the remote site to be consistent, but with multiple site masters, it's possible an update for the same key will go through a different route than the update before it. This violates the FIFO order and leads to inconsistent data between sites.

This is related to an issue in JGroups, which JBoss Data Grid uses. The issue won't be fixed in the version of JGroups that JDG 7.0.1 uses. The issue may be fixed in a future 7.1.x release of JDG, which uses a different version of JGroups.

This is a known issue in JBoss Data Grid 7.0.1, and to workaround this issue set max_site_master=1 in RELAY2.