When JBoss Cache is configured for INVALIDATION don't send cluster message on entity insert ------------------------------------------------------------------------------------------- Key: HHH-4484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4484 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 In the Hibernate/JBC integration, when EntityRegionAccessStrategy.insert is invoked and JBC is configured for INVALIDATION, the cache put should have the local-only option set. No other node is going to have this brand new entity cached, so sending out the invalidation message is a waste. This makes clustered 2nd level caching viable (i.e. performant) for a large category of entity types where it currently isn't; i.e. those that have a large number of inserts but not many updates after insert. -- 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