2 Replies Latest reply on Jul 8, 2007 6:43 PM by Mark Szymczak

    ejb 3.0 SFSB timeouts

    Mark Szymczak Newbie

      jboss-4.0.5.GA

      I am trying to get the container to destroy a test EJB 3.0 stateful bean.
      The client has not invoked the @Remove annotated method. It has just exited.

      Any changes that I make to standardjboss.xml seem to have no effect in so far as the bean is not passivated.

      When I add the

      @CacheConfig(maxSize=5, idleTimeoutSeconds=10)

      annotation, the bean is passivated rather quickly as expected but I cannot get the container to remove the bean. I would like to change a setting to force this to happen quickly so that I can see it.

      Any thoughts anyone ?

      Thanks in expectation.

        • 1. Re: ejb 3.0 SFSB timeouts
          Mark Szymczak Newbie

          Correction -

          Any changes that I make to standardjboss.xml seem to have no effect in so far as the bean is not passivated.


          Should be


          Any changes that I make to standardjboss.xml seem to have no effect.
          I cannot override the settings there.

          • 2. Re: ejb 3.0 SFSB timeouts
            Mark Szymczak Newbie

            Dear forum,

            I think that I can almost answer my own question.

            Looks like removal support was added with EJBTHREE-904 with removalTimeout on the @CacheConfig annotation.
            Looks like its only available in 4.2.0.GA ;-).

            Another question that I have is : Is it possible to know via the JMX console which container your SFSBeans have been deployed into and what the parameters of that container are ?

            Thankyou