Hi Kevin, It's strongly recommended that you don't mutate the instance that is already in cache. It can cause all different types of concurrency issues (for example, if it's concurrently serialized).
Actually, by default cache should create a copy each time you read the value. Did you set CacheConfiguration.copyOnRead property to false? If no, this can be a bug, please provide details on how you read from cache (code sample would be very useful as well). In any case, you can always manually create a copy before doing modifications. This should fix the behavior. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/A-Question-About-Behavior-tp3235p3237.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
