Timer service commands
Information about EJB timers is generally specific to the application that creates the timers, and the timers are not visible outside of the creating application. Therefore, management of EJB timers should be performed by the application that contains the enterprise bean, and that creates the EJB timer.
However, use the following commands during application development. They provide some basic EJB timer management functions. These commands are not available on client only installs.
findEJBTimers
This command displays information about existing EJB timers based on specified filter criteria.
The syntax for this command is
where :findEJBTimers server filter [options] filter: -all | -timer | -app [-mod [-bean ]] -all -timer timer id -app application name -mod module name -bean bean name options: -host host name -port portnumber -conntype connector type -user userid -password password -quiet -logfile filename -replacelog -trace -help
- server
- the name of the server process where the EJB timers are located
- -all
- find all EJB timers associated with the server process
- timer id
- EJB Timer ID that uniquely identifies the timer
- application name
- find all EJB timers associated with the application
- module name
- find all EJB timers associated with the module
- bean name
- find all EJB timers associated with the enterprise bean
- host name
- host name of the server process
- portnumber
- port of the server process
- connector type
- type of connection. For example, SOAP, RMI, or NONE.
- userid
- user to use when connecting to the server process
- password
- password to use when connecting to the server process
- quiet
- disable output
- logfile
- directs output to a file
- replacelog
- clears the existing log before executing the command
- trace
- enable trace
- help
- provides command-specific help
Note: If the server you specify is configured to use a scheduler instance that is shared by multiple servers, then EJB timers created in any of the server processes might be found.
For an example of the findEJBTimers command, see Example: FindEJBTimers command.
cancelEJBTimers
This command cancels and removes from persistent storage EJB timers based on the specified filter criteria.
The syntax for this command is
where :cancelEJBTimers server filter [options] filter: -all | -timer | -app [-mod [-bean ]] -all -timer timer id -app application name -mod module name -bean bean name options: -host host name -port portnumber -conntype connector type -user userid -password password -quiet -logfile filename -replacelog -trace -help
- server
- the name of the server process where the EJB timers are located
- -all
- find all EJB timers associated with the server process
- timer id
- EJB Timer ID that uniquely identifies the timer
- application name
- find all EJB timers associated with the application
- module name
- find all EJB timers associated with the module
- bean name
- find all EJB timers associated with the enterprise bean
- host name
- host name of the server process
- portnumber
- port of the server process
- connector type
- type of connection. For example, SOAP, RMI, or NONE.
- userid
- user to use when connecting to the server process
- password
- password to use when connecting to the server process
- quiet
- disable output
- logfile
- directs output to a file
- replacelog
- clears the existing log before executing the command
- trace
- enable trace
- help
- provides command-specific help
Note: If the server you specify is configured to use a scheduler instance that is shared by multiple servers, then EJB timers created in any of the server processes might be cancelled.
For an example of the cancelEJBTimers command, see Example: CancelEJBTimers command.
See also
Example: FindEJBTimers command
Example: CancelEJBTimers command