Example: F<?Pub Caret>indEJBTimers command

Example: FindEJBTimers command

The following examples illustrate how to use the command to find EJB timers and explain the output statement. To use the findEJBTimers command to find all EJB timers on a server called server1 :

findEJBTimers server1 -all

To find all EJB timers on server1 , associated with the Increment bean in the DefaultApplication :

findEJBTimers server1 -app DefaultApplication.ear -mod Increment.jar -bean Increment

When EJB timers matching the filter criteria are found, the output appears similar to this:

EJB Timer : 25     Expiration: Mon Feb 09 13:36:47 CST 2004   Repeating  EJB        : DefaultApplication.ear Increment.jar Increment  EJB Key: 8
 Info : Increment Counter EJB Timer : 26     Expiration: Mon Feb 09 13:36:47 CST 2004   Single  EJB        : DefaultApplication.ear Increment.jar Increment  EJB Key: 8
 Info : Decrement Counter 2 EJB Timers found

In this output:

The EJB Timer is the unique identifier of the timer.
Expiration is the next time the timer is expected to execute.
Repeating or Single indicates whether the EJB timer is single action or repeating.
EJB Key is the toString() method output of the primary key for the Entity enterprise bean (not present for other EJB types).
Info is the toString() method output of the object passed by the application when the EJB timer was created.

Only the first 40 bytes of toString() output are displayed for the Primary Key and Timer Info. This information is only useful if the application overrides the toString() method for these objects.

Increment in the DefaultApplication does not implement the TimedObject interface, and so could not actually have associated EJB Timers. Increment is used merely for illustrative purposes in this example.

Related reference
Example: Timer Service

Related information