2 Replies Latest reply on Dec 28, 2001 3:11 PM by Sacha Labourey

    Strange Stateful Session bean problem

    Milind Phadke Newbie

      I am getting the following exception
      ********************************************
      Root cause:
      java.lang.reflect.UndeclaredThrowableException: java.rmi.NoSuchObjectException:
      Could not activate; nested exception is:
      java.io.FileNotFoundException: /usr/JBoss-2.4.3_Tomcat-3.2.3/jboss/db/se
      ssions/PolicyTopoMgrApp/1009554815090.ser (No such file or directory)
      at org.jboss.ejb.plugins.AbstractInstanceCache.get(AbstractInstanceCache
      .java:211)
      at org.jboss.ejb.plugins.StatefulSessionInstanceInterceptor.invoke(State
      fulSessionInstanceInterceptor.java:194)
      at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:195)
      at org.jboss.ejb.StatefulSessionContainer.invoke(StatefulSessionContaine
      r.java:341)
      at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke(JRMPCon
      tainerInvoker.java:489)
      at org.jboss.ejb.plugins.jrmp.interfaces.GenericProxy.invokeContainer(Ge
      nericProxy.java:335)
      at org.jboss.ejb.plugins.jrmp.interfaces.StatefulSessionProxy.invoke(Sta
      tefulSessionProxy.java:136)
      at $Proxy73.cancelCheckoutForEdit(Unknown Source)
      ************************************************
      I am using the standardjobss.xml LRU passivation configuration. This exception happens within 1 or 2 minutes of starting Jboss. As per the configuration the SFSB should not have been passivated yet. But looks like the container believes ( incorrectly IMHO) that the bean has been passivated. Is this possible??
      One more thing I want to point out is there is no problem with passivation bcause If I create few more instances of theis bean and wait for approx. 30 mins, I see some instances correctly passivated ( *.ser files). Any idea what is going on???? TIA,
      - Milind