"jason.greene(a)jboss.com" wrote : I would need to handle puts as well, since I can't predict how someone is using POJO Cache. They could retrieve an object, wait for some period time (during which the data has been gravitated to another node), then trigger an update which would fail. | Although, in order to solve another problem, I have to do a read before almost every put to validate that the pojo hasn't been detached by a remote node (see JBCACHE-1057). So just forcing gravitation on reads will work, although the behavior and performance will match autoDataGravitation=true. I guess a strong reason against requiring autoDataGravitation is that like in your case, you might want to mix cache and pojocache calls in the same cache instance. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056719#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...