21.3.2 Life cycle of TimerManager

This section describes a life cycle of TimerManager.

TimerManager is created when lookup is performed by JNDI in an application. TimerManager is created for each lookup. We recommend that you execute the stop method in the application and explicitly stop the created TimerManager. TimerManager can be automatically stopped without executing the stop method. However, in that case, the application does not stop until TimerManager stops. Therefore, stopping the application might take a longer time, depending on the stop process of TimerManager.

TimerManager is not persisted. As a result, when JavaVM ends, the created TimerManager and scheduled timer are destroyed.

The following figure shows the life cycle of TimerManager.

Figure 21‒5:  Life cycle of TimerManager

To Page Top