2 Replies Latest reply on Sep 9, 2002 5:20 PM by Dain Sundstrom

    Does option D really work in 3.0.1 ?

    Tjodolf Newbie

      We cant get option D to work. Is there a problem with this option, or is it us that have configured the system wrong. Accordning to the logs the entity is reloaded everytime and is not cached for 900 seconds as we have specified. Our specifications in jboss.xml

      <ejb-name>WorldReadEJB</ejb-name>
      <jndi-name>se.jadestone.tm.world.ejb.WorldRead</jndi-name>
      <read-only>true</read-only>
      <configuration-name>CMP read-only</configuration-name>


      <container-configuration>
      <container-name>BMP read-only</container-name>
      <call-logging>false</call-logging>
      <container-invoker>org.jboss.proxy.ejb.ProxyFactory</container-invoker>
      <container-interceptors>
      org.jboss.ejb.plugins.LogInterceptor
      org.jboss.ejb.plugins.SecurityInterceptor
      org.jboss.ejb.plugins.TxInterceptorCMT
      org.jboss.ejb.plugins.MetricsInterceptor
      org.jboss.ejb.plugins.EntityCreationInterceptor
      org.jboss.ejb.plugins.EntityLockInterceptor
      org.jboss.ejb.plugins.EntityInstanceInterceptor
      org.jboss.resource.connectionmanager.CachedConnectionInterceptor
      org.jboss.ejb.plugins.EntitySynchronizationInterceptor
      </container-interceptors>
      <client-interceptors>

      org.jboss.proxy.ejb.HomeInterceptor
      org.jboss.proxy.SecurityInterceptor
      org.jboss.proxy.TransactionInterceptor
      org.jboss.invocation.InvokerInterceptor


      org.jboss.proxy.ejb.EntityInterceptor
      org.jboss.proxy.SecurityInterceptor
      org.jboss.proxy.TransactionInterceptor
      org.jboss.invocation.InvokerInterceptor

      <list-entity>
      org.jboss.proxy.ejb.ListEntityInterceptor
      org.jboss.proxy.SecurityInterceptor
      org.jboss.proxy.TransactionInterceptor
      org.jboss.invocation.InvokerInterceptor
      </list-entity>
      </client-interceptors>
      <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
      <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
      <persistence-manager>org.jboss.ejb.plugins.BMPPersistenceManager</persistence-manager>
      <transaction-manager>org.jboss.tm.TxManager</transaction-manager>
      <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
      <container-cache-conf>
      <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
      <cache-policy-conf>
      <min-capacity>50</min-capacity>
      <max-capacity>1000000</max-capacity>
      <overager-period>300</overager-period>
      <max-bean-age>600</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-pool-conf>
      100
      </container-pool-conf>
      <commit-option>D</commit-option>
      <optiond-refresh-rate>900</optiond-refresh-rate>
      </container-configuration>

      </container-configurations>

        • 1. Re: Does option D really work in 3.0.1 ?
          Tjodolf Newbie

          Sorry, but I put the wrong part of jboss-xml in there... Here is the CMP spec:

          <container-configuration>
          <container-name>CMP read-only</container-name>
          <call-logging>false</call-logging>
          <container-invoker>org.jboss.proxy.ejb.ProxyFactory</container-invoker>
          <container-interceptors>
          org.jboss.ejb.plugins.LogInterceptor
          org.jboss.ejb.plugins.SecurityInterceptor
          org.jboss.ejb.plugins.TxInterceptorCMT
          org.jboss.ejb.plugins.MetricsInterceptor
          org.jboss.ejb.plugins.EntityCreationInterceptor
          org.jboss.ejb.plugins.EntityLockInterceptor
          org.jboss.ejb.plugins.EntityInstanceInterceptor
          org.jboss.resource.connectionmanager.CachedConnectionInterceptor
          org.jboss.ejb.plugins.EntitySynchronizationInterceptor
          </container-interceptors>
          <client-interceptors>

          org.jboss.proxy.ejb.HomeInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.proxy.TransactionInterceptor
          org.jboss.invocation.InvokerInterceptor


          org.jboss.proxy.ejb.EntityInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.proxy.TransactionInterceptor
          org.jboss.invocation.InvokerInterceptor

          <list-entity>
          org.jboss.proxy.ejb.ListEntityInterceptor
          org.jboss.proxy.SecurityInterceptor
          org.jboss.proxy.TransactionInterceptor
          org.jboss.invocation.InvokerInterceptor
          </list-entity>
          </client-interceptors>
          <instance-pool>org.jboss.ejb.plugins.EntityInstancePool</instance-pool>
          <instance-cache>org.jboss.ejb.plugins.EntityInstanceCache</instance-cache>
          <persistence-manager>org.jboss.ejb.plugins.jaws.JAWSPersistenceManager</persistence-manager>
          <transaction-manager>org.jboss.tm.TxManager</transaction-manager>
          <locking-policy>org.jboss.ejb.plugins.lock.QueuedPessimisticEJBLock</locking-policy>
          <container-cache-conf>
          <cache-policy>org.jboss.ejb.plugins.LRUEnterpriseContextCachePolicy</cache-policy>
          <cache-policy-conf>
          <min-capacity>50</min-capacity>
          <max-capacity>1000000</max-capacity>
          <overager-period>300</overager-period>
          <max-bean-age>600</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-pool-conf>
          100
          </container-pool-conf>
          <commit-option>D</commit-option>
          <optiond-refresh-rate>900</optiond-refresh-rate>
          </container-configuration>

          • 2. Re: Does option D really work in 3.0.1 ?
            Dain Sundstrom Master

            There is a bug report on this I haven't looked at yet. It should work, but I haven't personally tested it yet.