As far as I know operations on atomic caches are applied immediately dishonoring any tx context.
I would suggest that atomic cache update operation called from active tx throws illegal state exception, unless user intentionally permits this update by calling atomicCache.withAllowInTx() (similar to withSkipStore()). Thoughts? --Yakov
