"The timer service is intended for the modelling of long-lived business processes. Timers survive container crashes, server shutdown, and the activation/passivation and load/store cycles of the enterprise beans that are registered with them."
The above is quoted from EJB Core Contracts and Requirements. I think here is a mistake because the EJB Core also says that timer cannot be created for stateful session beans or EJB 3.0 Entities. The activation/passivation belongs only to stateful session beans, right?
In the same page, there's a note . It says that it is not yet supported by stateful session beans, but "this functionality may be added in a future release of this specification.". So the spec says that the timer service will survive even after a passivation, but it doesn't say that it is used yet