Previously in Red Hat JBoss Data Grid, when a persistent cache store was used with Passivation, the <command>remove</command> command did not activate the entry in cache store, which resulted in an inconsistency because the entry was never removed. It was removed from internal DataContainer but not from the cache store and during any operation, the old value could be loaded from the cache store back again. This is fixed in JBoss Data Grid 6.3.1 and the remove operation now works correctly.
The RemoveCommand does not activate the key in CacheStore. This creates an inconsistency because the key is never really removed. More precisely, the key is removed from DataContainer but not from CacheStore and during any operation, the old value is loaded from the CacheStore.
Verified with JDG 6.3.1 ER2