Passivation can miss entries with size optimization/iteration and a concurrent operation

Passivation will move an entry into a store when it is evicted. We ensure this value is consistent for individual key retrieval (DataOperationOrderer).

However, for iteration there is an issue that if the entry is evicted while still doing the write it can cause an issue where the entry is not counted. This can happen much more often with a newer version of caffeine introduced in https://issues.redhat.com/browse/ISPN-15555.

Size optimization has a different issue where it can miss entries temporarily because PassivationPersistenceManager's temporary map is not used for size calculation.