[ https://issues.jboss.org/browse/WFLY-12814?page=com.atlassian.jira.plugin... ] Cheng Fang updated WFLY-12814: ------------------------------ Description: When a stateful bean is configured to have timeout value 0, its preDestroy method is not called when removing it. The expected behavior is the bean should timeout and be eligible for removal immediately (since the stateful timeout is 0), and its preDestroy method is called before the bean is removed. The problem seems to be in {{org.jboss.as.ejb3.cache.simple.SimpleCache}}, which removes the bean with 0 timeout value directly, instead of submitting it to {{org.wildfly.clustering.ee.cache.scheduler.LocalScheduler}} for removal. The direct removal does not have all the proper setup for the preDestroy method to be invoked. {code:java} @Stateful @StatefulTimeout(value = 0, unit = TimeUnit.SECONDS) //when changed @StatefulTimeout to 1, it works as expected. //@StatefulTimeout(value = 1, unit = TimeUnit.SECONDS) public class StatefulHello { public void hello() { } @PreDestroy private void preDestroy() { System.out.printf("## preDestroy in StatefulHello%n"); } } {code} was: When a stateful bean is configured to have timeout value 0, its preDestroy method is not called when removing it. The expected behavior is the bean should timeout and be eligible for removal immediately (since the stateful timeout is 0), and its preDestroy method is called before the bean is removed. The problem seems to be in {{org.jboss.as.ejb3.cache.simple.SimpleCache}}, which removes the bean with 0 timeout value directly, instead of submitting it to {{org.wildfly.clustering.ee.cache.scheduler.LocalScheduler}} for removal. The direct removal does not have all the proper setup for the preDestroy method to be invoked. -- This message was sent by Atlassian Jira (v7.13.8#713008)