[ https://issues.jboss.org/browse/ISPN-4134?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4134: ------------------------------------ I guess making {{Cache.evict()}} cluster-wide would be a natural evolution of what we've been doing so far. {{evict()}} now behaves more or less like a regular {{remove()}} that writes the entry to the cache instead of removing it (or just skips the cache store, if passivation is disabled). But the javadoc hasn't changed a lot since the beginning of the project, and it paints a completely different picture: {noformat} * This method is designed to evict an entry from memory to free up memory used by the application. This method uses * a 0 lock acquisition timeout so it does not block in attempting to acquire locks. It behaves as a no-op if the * lock on the entry cannot be acquired <i>immediately</i>. * <p/> * Important: this method should not be called from within a transaction scope. {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira