[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=all ] Galder Zamarreno updated EJBTHREE-844: -------------------------------------- Description: Currently, EJB3/Hibernate cannot take advantage of using a second level cache based in optimistic locking in a EJB3 environment. We only have a TreeCacheProviderHook CacheProvider for pessimistic locking which means that if a customer wants to set up optimistic locking, it's forced to use OptimisticTreeCacheProvider. However, this class was not designed for managed environments and ends up creating another cache, so you end up with two caches for the same job in the same instance which is wrong. I have created a OptimisticTreeCacheProviderHook which creates an org.hibernate.cache.OptimisticTreeCache based on the TreeCacheMBean instance looked up. Please find attached. This could be improved by creating a accessor method for TreeCacheProviderHook.cache, so that I can directly extend it rather than reimplementing CacheProvider. But, I have followed the CacheProvider implementation path so that I can quickly send a patched jar to the customer containing just this class. was: Currently, EJB3/Hibernate cannot take advantage of using a second level cache based in optimistic locking in a EJB3 environment. We only have a TreeCacheProviderHook CacheProvider for pessimistic locking which means that if a customer wants to set up optimistic locking, it's forced to use OptimisticTreeCacheProvider. However, this class was not designed for managed environments and ends up creating another cache, so you end up with two caches for the same job in the same instance which is wrong. I have created a OptimisticTreeCacheProviderHook which creates an org.hibernate.cache.OptimisticTreeCache based on the TreeCacheMBean instance looked up. Please find attached. This could be improved by creating a accessor method for TreeCacheProviderHook.cache, so that I can directly extend it rather than reimplementing CacheProvider. But, I have gone followed the CacheProvider implementation path so that I can quickly pass a patched jar containing this class only to the customer for them to try. -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=comments#action_12352717 ] Brian Stansberry commented on EJBTHREE-844: ------------------------------------------- Galder, if you're going to do this for RC10, make sure you are completely clear on EJBTHREE-798 and that your fix deals with and tests those issues. See class org.jboss.ejb3.entity.JBCCache for the pessimistic locking implementation. -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=all ] Galder Zamarreno updated EJBTHREE-844: -------------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC11 - FD) -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=all ] Brian Stansberry resolved EJBTHREE-844. --------------------------------------- Resolution: Done Added class org.jboss.ejb3.entity.OptimisticJBCCache that implements for OptimisticTreeCache the same EJBTHREE-798 fixes the JBCCache does for pessimistic locking. TreeCacheProviderHook is now agnostic as to whether optimistic or pessimistic locking is used. It simply checks the JBoss Cache configuration and provides instances of OptimisticJBCCache or JBCCache based on what it finds. OptimisticTreeCacheProviderHook was added in order to have a logical parallel to the Hibernate OptimisticTreeCacheProvider class. It really doesn't add anything beyond TreeCacheProviderHook though, other than logging a warning if it discovers JBoss Cache is configured for pessimistic locking. -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=all ] William DeCoste reopened EJBTHREE-844: -------------------------------------- -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-844?page=all ] William DeCoste updated EJBTHREE-844: ------------------------------------- SourceForge Reference: https://na1.salesforce.com/500300000033UhQ -- 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