3 Replies Latest reply on Nov 1, 2003 3:35 AM by adrian.brock

    The system cannot find the file specified

    dries.demoor

      Hello,

      Sometimes I get an error like this:

      15:58:14,812 ERROR [DataCollector] demoord Could not activate; CausedByException is:
      C:\JavaTools\jboss-3.0.4_tomcat-4.1.12\server\default\db\sessions\VerfkeukenBean\1067595369275.ser (The system cannot find the file specified)
      java.rmi.NoSuchObjectException: Could not activate; CausedByException is:
      C:\JavaTools\jboss-3.0.4_tomcat-4.1.12\server\default\db\sessions\VerfkeukenBean\1067595369275.ser (The system cannot find the file specified)


      Can somebody tell me when or why this error is occurring? In the VerfkeukenBean class I declare some ResourceBundle as static final , and one Logger as static final transient. Can this cause some problems when the session bean is activated after passivation?


      Thanks a lot,


      Dries

        • 1. Re: The system cannot find the file specified

          The stateful session bean has timeout.

          The default is passivate the bean to disk after 10 minutes,
          and remove after 30 minutes.

          See standardjboss.xml

          Regards,
          Adrian

          • 2. Re: The system cannot find the file specified
            dries.demoor

            Hello,


            If I understand well, the bean is passicate after 10 minutes and after 30 minutes the Bean is removed, if there is no call to it.

            If you call the bean when it is already removed by JBoss should create a new instance I guess? So the Exception I got prooves that this is not the case. It is trying to read the serialized Bean but it is removed?

            So increasing those values will help me for a while but the problem will still occur but no that fast?

            Is this correct? Are there other sollutions?

            Kind regards,


            Dries

            • 3. Re: The system cannot find the file specified

              No JBoss will not re-create the instance after it has been
              removed.

              How can it? It does not have the state of the removed bean,
              the state is gone.

              Increase the lifetime to whatever is appropriate.
              It is a tradeoff between how long idle sessions last
              and how much disk space is used storing that information.

              Regards,
              Adrian