Information about Enterprise JavaBeans (EJB) timers is specific to the
application that the timers are created for, and the timers are not
visible outside of that application. Therefore, when you manage EJB
timers, use the application that contains the enterprise bean and
creates the EJB timer.
You can use the following commands during application development
to provide basic EJB timer management functions. These commands are not available
on client only installations.
findEJBTimers
This
command displays information about existing persistent EJB timers,
based on specified filter criteria.
This command displays information about existing persistent
EJB timers, based on specified filter criteria. The syntax for this
command is:
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
The following options exist:
- server
- Specifies the name of the server process where the EJB timers
are located
- -all
- Specifies to find all EJB timers associated with the server process
- timer id
- Specifies the EJB Timer ID that uniquely identifies the timer
- application name
- Specifies to find all EJB timers associated with the application
- module name
- Specifies to find all EJB timers associated with the module
- bean name
- Specifies to find all EJB timers associated with the enterprise
bean
- host name
- Specifies the host name of the server process
- portnumber
- Specifies the port of the server process
- connector type
- Specifies the type of connection. For example, SOAP, RMI, or NONE.
- userid
- Specifies the user to use when connecting to the server process
- password
- Specifies the password to use when connecting to the server process
- quiet
- Specifies to disable output
- logfile
- Specifies to direct output to a file
- replacelog
- Specifies to clear the existing log before executing the command
- trace
- Specifies to enable trace
- help
- Specifies to provide 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 that are created in any of the server
processes might be found.
See the information
about locating EJB timers using the findEJBTimers command.
cancelEJBTimers
This
command cancels and removes from persistent storage EJB persistent
timers based on the specified filter criteria.
The syntax for this command is:
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
the following options exist:
- server
- Specifies the name of the server process where the EJB timers
are located
- -all
- Specifies to find all EJB timers associated with the server process
- timer id
- Specifies the EJB Timer ID that uniquely identifies the timer
- application name
- Specifies to find all EJB timers associated with the application
- module name
- Specifies to find all EJB timers associated with the module
- bean name
- Specifies to find all EJB timers associated with the enterprise
bean
- host name
- Specifies the host name of the server process
- portnumber
- Specifies the port of the server process
- connector type
- Specifies the type of connection. For example, SOAP, RMI, or NONE.
- userid
- Specifies the user to use when connecting to the server process
- password
- Specifies the password to use when connecting to the server process
- quiet
- Specifies to disable output
- logfile
- Specifies to direct output to a file
- replacelog
- Specifies to clear the existing log before executing the command
- trace
- Specifies to enable trace
- help
- Specifies to provide 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 that are created in any of the server
processes might be canceled.
For an example
of the cancelEJBTimers command, see the topic CancelEJBTimers command
example.