[jboss-jira] [JBoss JIRA] (EJBTHREE-2275) PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached

[Brad Maxwell (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/EJBTHREE-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Maxwell updated EJBTHREE-2275:
-----------------------------------

    Affects Version/s: bom-eap5-1.0.3
                           (was: bom-eap5-1.0.2)

    
> PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached
> --------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-2275
>                 URL: https://issues.jboss.org/browse/EJBTHREE-2275
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: bom-eap5-1.0.3
>            Reporter: Brad Maxwell
>            Assignee: Brad Maxwell
>             Fix For: TBD EAP 5
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira