The activation does not interact with the shared cache store. This creates a problem for the RemoveCommand (at least) since the value is never removed (similar to https://issues.jboss.org/browse/ISPN-4649)
Unfortunately, this will need a little more thinking how to solve it since only the primary owner should activate (i.e. remove it) from the shared store.
Tests in LocalConditionalCommandTest and ClusteredConditionalCommandTest are disabled to because they are hitting this issue.
(ps to myself: don't forget to re-enabled them)