-
Bug
-
Resolution: Done
-
Major
-
bom-eap5-1.0.3
-
None
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.
- is cloned by
-
JBPAPP-7724 PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached
- Closed
- is incorporated by
-
JBPAPP-7724 PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached
- Closed