anonymous wrote : One solution I thought of was to have TreeCache set a boolean value in a ThreadLocal in _clusteredGet and _dataGravitationCleanup. A cache listener could then check for the ThreadLocal and ignore events that arise from data gravitation. Kinda hacky though. Should node removals originating from data gravitation cleanups emit notifications in the first place? I suppose so, for correctness and predictability of behaviour. What about an additional parameter to the remove notification, to indicate whether the remove is cluster-wide (i.e., a REAL remove) or local (i.e., a data gravitation cleanup)? This would be a 2.0.0 fix though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3975471#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...