Sun GlassFish Enterprise Server 2.1 Developer's Guide

EJB Timer Service

The EJB Timer Service uses a database to store persistent information about EJB timers. In the developer profile, the EJB Timer Service in Enterprise Server is preconfigured to use an embedded version of the Java DB database. The EJB Timer Service configuration can store persistent timer information in any database supported by the Enterprise Server for persistence.

For a list of the JDBC drivers currently supported by the Enterprise Server, see the Sun GlassFish Enterprise Server 2.1 Release Notes. For configurations of supported and other drivers, see Configurations for Specific JDBC Drivers in Sun GlassFish Enterprise Server 2.1 Administration Guide.

To change the database used by the EJB Timer Service, set the EJB Timer Service’s Timer DataSource setting to a valid JDBC resource. You must also create the timer database table. DDL files are located in as-install/lib/install/databases. Ideally, each cluster should have its own timer table.

Using the EJB Timer Service is equivalent to interacting with a single JDBC resource manager. If an EJB component or application accesses a database either directly through JDBC or indirectly (for example, through an entity bean’s persistence mechanism), and also interacts with the EJB Timer Service, its data source must be configured with an XA JDBC driver.

You can change the following EJB Timer Service settings. You must restart the server for the changes to take effect.

For information about configuring EJB Timer Service settings, see Chapter 8, SIP, Web, and EJB Containers, in Sun GlassFish Enterprise Server 2.1 Administration Guide. For information about the asadmin list-timers and asadmin migrate-timers commands, see the Sun GlassFish Enterprise Server 2.1 Reference Manual.