1 Reply Latest reply on May 21, 2003 5:37 AM by vakrishnan

    Problem using Cache Invalidation Framework

    vakrishnan

      Hi, I tried to use the Problem using Cache Invalidation Framework on JBoss-3.2.0, but a java.lang.NoSuchMethodError is thrown during deployment.

      I have the following snippet in my jboss.xml for a CMP bean:
      --START

      <ejb-name>ServiceChargeDetails</ejb-name>
      <jndi-name>com.dbs.lsr.entity.ServiceChargeDetailsHome</jndi-name>
      <local-jndi-name>com.dbs.lsr.entity.ServiceChargeDetailsLocalHome</local-jndi-name>
      <method-attributes>

      <method-name>get*</method-name>
      <read-only>true</read-only>

      </method-attributes>

      <configuration-name>Standard CMP 2.x EntityBean with cache invalidation</configuration-name>
      <cache-invalidation>True</cache-invalidation>

      --END

      The trace on screen is:
      --START
      19:50:52,313 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=com.dbs.lsr.entity.ServiceChargeDetailsHome,service=EJB
      java.lang.NoSuchMethodError: org.jboss.system.ServiceMBeanSupport.access$001(Lorg/jboss/cache/invalidation/InvalidationManager;)Lorg/jboss/logging/Logger;
      at org.jboss.cache.invalidation.InvalidationManager$InvalidationGroupImpl.addReference(InvalidationManager.java:387)
      at org.jboss.cache.invalidation.InvalidationManager.getInvalidationGroup(InvalidationManager.java:89)
      at org.jboss.ejb.plugins.InvalidableEntityInstanceCache.start(InvalidableEntityInstanceCache.java:107)
      at org.jboss.ejb.EntityContainer.startService(EntityContainer.java:336)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:966)
      at $Proxy11.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:392)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy267.start(Unknown Source)
      at org.jboss.ejb.EjbModule.startService(EjbModule.java:347)
      ....
      --END

      None of the forums seem to have a thread on cache invalidation. Can anyone give me some pointers?

      Thanks,
      vakrishnan.

        • 1. Re: Problem using Cache Invalidation Framework
          vakrishnan

          Never mind, I was able to fix it myself.

          It seems like the classes in the 3.2 release are not all in sync. The problem
          vanished when I recompiled org/jboss/cache/invalidation/InvalidationManager.java
          and updated jboss.jar in my server/all/lib/ with the new class files.

          - vakrishnan.