The following examples illustrate how to use the findEJBTimers command to find Enterprise JavaBeans (EJB) timers and explain the output statement. For relevant parameters and syntax information, read about the timer service commands.
To find all EJB timers on a server called server1, enter the following command in the <install-root>\profiles\<profile>\bin directory:
findEJBTimers server1 -all
To find all EJB timers on server1, associated with the Increment bean in the DefaultApplication, enter the following command in the <install-root>\profiles\<profile>\bin directory:
findEJBTimers server1 -app DefaultApplication.ear
-mod Increment.jar -bean Increment
When EJB timers matching the filter criteria are found, the output appears similar to the following:
EJB Timer : 252 Expiration: 5/25/10 10:53 AM Single EJB : TimerPtestApp, TimerPtestEJB.jar, NoMoreTimeoutsBean Info : Single Programmatic timer EJB Timer : 253 Expiration: 5/25/10 11:47 AM Calendar EJB : TimerPtestApp, TimerPtestEJB.jar, NoMoreTimeoutsBean Automatic timer Calendar expression: [start=null, end=null, timezone=null, seconds="52", minutes="47", hours="11", dayOfMonth="25", month="5", dayOfWeek="*", year="2010"] 2 EJB Timer tasks found
Only the first forty bytes of toString() output are displayed for the primary key and timer information. This information is only useful if the application overrides the toString() method for these objects.