TreeCacheProviderHook.isMinimalPutsEnabledByDefault() wrong ----------------------------------------------------------- Key: EJBTHREE-707 URL: http://jira.jboss.com/jira/browse/EJBTHREE-707 Project: EJB 3.0 Issue Type: Bug Reporter: Owen Taylor Priority: Minor org.jboss.ejb3.entity.TreeCacheProviderHook.isMinimalPutsEnabledByDefault() returns false, which means "don't check to see if values are in the cache before inserting them again", but that's a very bad setting for the TreeCache - It causes unnecessary replication between the nodes of a cluster - It tends to cause lock conflicts because the transaction putting data into the cache has to get a (briefly) get a write lock. There are hacky workarounds in the hibernate TreeCache code not to deadlock in this code, but you still get log spew. The TreeCacheProvider provided with Hibernate (no JMX integration) returns true isMinimalPutsEnabledByDefault() as it should, so I think this is just an oversight. You can of course easily work around the problem by setting the value explicitly in the hibernate properties. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira