0 Replies Latest reply on Jan 10, 2006 6:45 AM by Alberto Acinapura

    SimpleReadWriteEJBLock policy

    Alberto Acinapura Newbie

      Hi folks,
      I have a problem using SimpleReadWriteEJBLock with commit-option A in jboss-4.0.3:
      because of heavy load of my application, I need a different read/write locking policy, so I decided to use SimpleReadWriteEJBLock, but multiple access to the same EJB causes a "lock contention" until transaction expires for timeout.
      Other locking policies I tested (QueuedPessimisticEJBLock, cmp2.x jdbc2 pm) don't satisfy application required performance or don't resolve my problem.
      Can anyone help me?

      Thanks,
      Alberto

      P.S. This is my container configuration:

       <!-- Re-definition of Standard CMP 2.x EntityBean -->
       <container-configuration extends="Standard CMP 2.x EntityBean with cache invalidation">
       <container-name>Standard CMP 2.x EntityBean</container-name>
       <locking-policy>org.jboss.ejb.plugins.lock.SimpleReadWriteEJBLock</locking-policy>
       <container-cache-conf>
       <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
       <cache-policy-conf>
       <min-capacity>150</min-capacity>
       <max-capacity>1000000</max-capacity>
       <overager-period>600</overager-period>
       <max-bean-age>1200</max-bean-age>
       <resizer-period>400</resizer-period>
       <max-cache-miss-period>60</max-cache-miss-period>
       <min-cache-miss-period>1</min-cache-miss-period>
       <cache-load-factor>0.75</cache-load-factor>
       </cache-policy-conf>
       </container-cache-conf>
       </container-configuration>