Chapter 4. Known Issues

In Red Hat JBoss Data Grid’s library mode, JDBC cache stores can be configured to use a JTA-aware datasource. However, operations performed on a cache backed by such a store during a JTA transaction will be persisted to the store outside of the transaction’s scope. This issue is not applicable to JBoss Data Grid’s Remote Client-Server mode because all cache operations are non-transactional.

This is a known issue in JBoss Data Grid 6.3.1. No workaround is currently available for this issue.

In Red Hat JBoss Data Grid, SuspectExceptions are routinely raised when nodes are shutting down because they are unresponsive as they shut down. As a result, a SuspectException error is added to the logs. The SuspectExceptions do not affect data integrity.

This is a known issue in JBoss Data Grid 6.3.1. No workaround is currently available for this issue.

In Red Hat JBoss Data Grid, the CLI upgrade command fails to migrate data from the old cluster to the new cluster if the data being migrated was stored in the old cluster via CLI (for example, by issuing a command such as put --codec=hotrod key1 val1). This issue does not occur if data is stored via the Hot Rod or REST clients directly.

This is a known issue in JBoss Data Grid 6.3.1. There is currently no workaround for this solution.

In Red Hat JBoss Data Grid, JPA Cache Store does not work with Oracle12c and Postgres Plus 9 as Hibernate, an internal dependency of JPA Cache Store, is not able to determine which dialect to use for communication with the database.

This is an open issue in JBoss Data Grid 6.3.1. As a workaround for around this issue, specify the Hibernate dialect directly by adding the following element in the persistence.xml file:

<property name="hibernate.dialect" value="${hibernate.dialect}" />

Set ${hibernate.dialect} to org.hibernate.dialect.Oracle10gDialect or org.hibernate.dialect.PostgresPlusDialect for Oracle12c or Postgres Plus 9 respectively.

In Red Hat JBoss Data Grid, transactional caches are configured with optimistic locking by default. Concurrent replace() calls can return true under contention and transactions might unexpectedly commit.

Two concurrent commands, replace(key, A, B), replace(key, A, C) may both overwrite the entry. The command which is finalized later wins, overwriting an unexpected value with new value.

This is a known issue in JBoss Data Grid 6.3.1. As a workaround, enable write skew check and the REPEATABLE_READ isolation level. This results in concurrent replace operations working as expected.

In Red Hat JBoss Data Grid, when using put/remove operations via Hot Rod, some objects are not be indexed if the system is heavily loaded. These object are not returned by Remote Query or based on their previous state. This also affects embedded querying when the cache is not transactional.

This bug may also cause loss of update and delete operations, so while it’s true that subsequent queries might miss results of newly inserted objects, they might also contain results which aren’t supposed to be returned. The problem on missed delete operations only affects usage of projection, as when the user asks to return the object from the grid we remove the missing ones from the results.

This is a known issue in JBoss Data Grid 6.3.1. The workaround is to mark the cache transactional, regardless of the cache being accessed over Hot Rod (note that then every single operation is enclosed in a transaction) or locally as an embedded cache.

In Red Hat JBoss Data Grid, when a site is unreachable, JGroups’s RELAY2 logs an error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), but the log is filled with errors despite the ignore policy.

This is a known issue for JBoss Data Grid 6.3.1 and no workaround is currently available.

In Red Hat JBoss Data Grid, when special characters are used in the directory path, the JBoss Data Grid server either fails to start or a configuration file used for logging cannot be loaded properly. Special characters that cause problems include spaces, # (hash sign), ! (exclamation mark), % (percentage sign), and $ (dollar sign).

This is a known issue in JBoss Data Grid 6.3.1. A workaround for this issue is to avoid using special characters in the directory path.

Currently, it is not possible to create a remote cache store child resource for a cache using the JBoss Data Grid Remote Client-Server plug-in for JBoss Operation Network. The operation subsequently fails and the JBoss Operations Network Agent records the failure in its log file. As a result, a remote cache store cannot be configured using the JBoss Operations Network user interface.

This is a known issue in JBoss Data Grid 6.3.1. As a workaround for this issue, modify the JBoss Data Grid server configuration file to manually configure the remote cache store.