Prevent user from configuring passivation with a shared store

Passivation only makes sense with a non shared cache store. -The problem is that if an entry is passivated on a shared cache store only the first node will be able to activate the entry and subsequent nodes will always see null.-

Looking closer the bigger issue is if an entry becomes passivated and then subsequently written to you will have a different value in the store as you would in memory.