-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: EAP_EWP 5.1.2
-
Fix Version/s: EAP_EWP 5.2.0
-
Component/s: EJB
-
Labels:None
-
Affects:Release Notes
-
Release Notes Text: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.
-
Release Notes Docs Status:Documented as Resolved Issue
-
Docs QE Status: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.
- cloned to
-
EJBTHREE-2275 PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached
-
- Resolved
-
- incorporates
-
EJBTHREE-2275 PreDestroy lifecycle callback not called when Activated EJB3 SFSB removal timeout is reached
-
- Resolved
-
- is incorporated by
-
JBPAPP-7578 Upgrade jboss-ejb3-bom-eap5 to 1.0.4
-
- Closed
-