Chapter 6. Known Issues
6.1. Known Issues
Find out about known issues and available workarounds in this release of Red Hat JBoss Data Grid.
- Cannot Apply Patches to JBoss Data Grid Server If the 7.2.2 Patch Is Applied
Issue: JDG-2178
Description: If you have applied the patch for JBoss Data Grid 7.2.2, you must first revert that patch back before you apply the patch for JBoss Data Grid 7.2.3 or later. You cannot apply patches for subsequent releases on top of JBoss Data Grid 7.2.2.
Workaround: Revert the patch for JBoss Data Grid 7.2.2 as follows:
$ bin/cli.sh "patch rollback --patch-id=jboss-jdg-7.2.2.CP --reset-configuration=false"
- JBoss Data Grid Does Not Start and NullPointerException Occurs if Persistent Location is Not Unique
Issue: JDG-1504
Description: It is not possible to start more than one instance of JBoss Data Grid from the same directory if the value of
persistent-locationis not unique in each configuration.Workaround: Do one of the following to ensure the value of
persistent-locationis unique in the JBoss Data Grid configuration:Set a unique
pathattribute for each instance.<persistent-location path="mydir${uniquesuffix}" />Set a unique
relative-toattribute for each instance if using a common path:<paths> <path name="mypath" path="/home/user/jboss-datagrid-7.2.0-server/standalone/mypath" /> </paths> <persistent-location relative-to="mypath" path="mydir" />
Specify the
-Djboss.server.data.dirsystem property to set a unique relative location for each instance if using a common path:./standalone.sh -Djboss.server.data.dir=/home/user/jboss-datagrid-7.2.0-server/standalone/mypath
- SKIP_CACHE_LOAD Flag Has No Effect if Authentication is Enabled
Issue: JDG-1424
Description: In Remote Client-Server mode, if you set the
SKIP_CACHE_LOADflag 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.
- Intermittent Data Loss Occurs During Rolling Upgrades Between Clusters
Issue: JDG-991
Description: When performing a rolling upgrade of JBoss 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.
- Cluster Actions Disabled on JBoss Data Grid Administration Console in Reload-Required State
Issue: JDG-1843
Description: Actions available for the JBoss 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-Requiredstate.ReloadandStopactions are available for each node in the cluster.Workaround: Reload at least one node in the cluster to restore actions at the cluster level.
- Errors Occur When Changing the Eviction Strategy from the JBoss Data Grid Administration Console
Issue: JDG-1804
Description: If JBoss 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.
- NullPointerException Occurs When Reading Data from Persistent Storage in JBoss Data Grid 7.0 and Earlier
Issue: JDG-968
Description: If you store data in a cache store with JBoss Data Grid 7.0 and earlier and then attempt to read that data with JBoss Data Grid 7.1 or later, an error occurs and it is not possible to read the data.
NoteThis issue does not apply when upgrading from JBoss Data Grid 7.1 to 7.2.
Workaround: There is no workaround for this issue.
