Configuring the EJB Timer Service Settings

The timer service is a persistent and transactional notification service provided by the enterprise bean container used to schedule notifications or events used by enterprise beans. All enterprise beans except stateful session beans can receive notifications from the timer service. Timers set by the service are not destroyed when the server is shut down or restarted.

To configure the EJB Timer Service using the Admin Console, go to Configuration > EJB Container > EJB Timer Service.

• Set the minimum delivery interval in milliseconds in the Minimum Delivery Interval field.

  Minimum Delivery Interval is the minimum number of milliseconds allowed before the next timer expiration for a particular timer can occur. Setting this interval too low can cause server overload.

• Set the maximum number of attempts the timer service makes to deliver the notification in the Maximum Redeliveries field.

• Set the interval, in milliseconds, between redelivery attempts in the Redelivery Interval field.

• Specify the JNDI name of the JDBC resource that will be used as the Timer Datasource.

• Restart the Application Server.

Using an External Database With the Timer Service

By default, the timer service uses an embedded database to store timers. You can set up the timer service to another database.

Sample timer database creation files are provided for Java DB (Derby), PointBase, Oracle, Sybase, DB2, and MS SQL Server at install-dir/lib/install/databases/.

To use an external database with the Timer Service, first, set up a JDBC resource for the selected database as described in Creating a JDBC Resource. Then go to Configuration > EJB Container > EJB Timer Service and enter the JNDI name of the resource in the Timer DataSource field. Restart the Application Server.

See the following for related information:

• Creating a JDBC Resource

• Chapter 5, JNDI Resources

• The EJB Container