[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4517?page=c... ] Brian Stansberry commented on HHH-4517: --------------------------------------- I don't see a good solution to this. With JBC configured for invalidation (the norm with entity/collection caches) there's no way to communicate to other nodes that they should evict data, except by actually removing the data. And removing the data requires acquiring a lock, which JBC won't allow "without regard to transactional isolation." The existing impl removes the data, which I think is as good as we can do. Fortunately, the evict(Object) method is not itself called by Hibernate as part of normal processing. This is unlike evictAll() which gets called anytime bulk HQL is executed. The evict(Object) is only called as a result of the application attempting to directly manipulating the cache via the SessionFactory API. I haven't seen any reports of users having problems with this, probably because directly manipulating the cache isn't common and those who do so aren't concerned about the "without regard to transactional isolation" semantic. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira