Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-7724

PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP_EWP 5.2.0
    • EAP_EWP 5.1.2
    • EJB
    • None
    • Release Notes
    • If a Stateful Session Bean reached its removalTimeout, the system removed the bean without executing the @PreDestroy lifecycle. JBoss will now execute the @PreDestroy annotated method of the Stateful Session Bean before removing the bean.
    • Documented as Resolved Issue
    • NEW

      If removalTimeout < idleTimeout then the @PreDestroy callback is not called such as:
      @org.jboss.ejb3.annotation.CacheConfig(maxSize=1,idleTimeoutSeconds=5,removalTimeoutSeconds=1)

      If the removalTimeout > idleTimeout, then it functions as expected:
      INFO [STDOUT] helloWorld-ejb.jar - PostConstruct
      INFO [STDOUT] helloWorld-ejb.jar - Passivate
      INFO [STDOUT] helloWorld-ejb.jar - Activate
      INFO [STDOUT] helloWorld-ejb.jar - Destroy

      When removalTimeout < idleTimeout, if the RemovalTimeoutTask finds the removalTimeout has been reached for a particular SFSB, then it should go from Activated state to PreDestory to non-existent.

        1. JBPAPP-7724.zip
          6 kB

              rhn-support-bmaxwell Brad Maxwell
              rhn-support-bmaxwell Brad Maxwell
              Eva Kopalova Eva Kopalova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: