Question on Schedule Execution of Business Logic using Automatic Timers

[Mohit G Gupta]

Source 12.1.3. Running the Example Program – Declarative Scheduling

OCP JavaEE 6 EJB Developer Study Notes by Ivan A Krizsan Version: April 8, 2012

I had modified the example on Eclipse as below:

@Schedule(second = "20, 45", minute = "*", hour = "6-23",
dayOfWeek = "Mon-Sun", dayOfMonth = "*", month = "*", year = "*",
info = "MyTimer")
private void scheduledMethod1(final Timer inTimer)

Below is the output :

INFO: TimerExample was successfully deployed in 588 milliseconds.

INFO: ScheduledStatelessSessionBean created: 2 at: Sat Mar 23 22:58:25 IST 2013
INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 22:58:25 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 22:58:27 IST 2013

INFO: Updating configuration from org.apache.felix.fileinstall-autodeploy-bundles.cfg
INFO: Installed E:\Applications\GlassFish\glassfishv3\glassfish\modules\autostart\org.apache.felix.fileinstall-autodeploy-bundles.cfg
INFO: {felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir = E:\Applications\GlassFish\glassfishv3\glassfish\domains\domain1\autodeploy\bundles, felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true, felix.fileinstall.tmpdir = C:\Users\MOHITG~1\AppData\Local\Temp\fileinstall--6983556870689788337, felix.fileinstall.filter = null}

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 22:58:35 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 22:58:37 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 entering at: Sat Mar 23 22:58:45 IST 2013
INFO: ScheduledStatelessSessionBean created: 3 at: Sat Mar 23 22:58:45 IST 2013
INFO:  Rollback only: false
INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 22:58:45 IST 2013
INFO:  Timer info: MyTimer

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 22:58:47 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 22:58:55 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 22:58:57 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 exiting at: Sat Mar 23 22:59:00 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 22:59:15 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 22:59:17 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 entering at: Sat Mar 23 22:59:20 IST 2013
INFO:  Rollback only: false
INFO:  Timer info: MyTimer

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 22:59:25 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 22:59:27 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 22:59:35 IST 2013
INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 exiting at: Sat Mar 23 22:59:35 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 22:59:37 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 22:59:45 IST 2013
INFO: ScheduledStatelessSessionBean.scheduledMethod1: 3 entering at: Sat Mar 23 22:59:45 IST 2013
INFO:  Rollback only: false
INFO:  Timer info: MyTimer

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 22:59:47 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 22:59:55 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 22:59:57 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 3 exiting at: Sat Mar 23 23:00:00 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 23:00:15 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 23:00:17 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 3 entering at: Sat Mar 23 23:00:20 IST 2013
INFO:  Rollback only: false
INFO:  Timer info: MyTimer

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 23:00:25 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 23:00:27 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 entering at: Sat Mar 23 23:00:35 IST 2013
INFO: ScheduledStatelessSessionBean.scheduledMethod1: 3 exiting at: Sat Mar 23 23:00:35 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 2 exiting at: Sat Mar 23 23:00:37 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 23:00:45 IST 2013
INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 entering at: Sat Mar 23 23:00:45 IST 2013
INFO:  Rollback only: false
INFO:  Timer info: MyTimer

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 23:00:47 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 entering at: Sat Mar 23 23:00:55 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod2: 3 exiting at: Sat Mar 23 23:00:57 IST 2013

INFO: ScheduledStatelessSessionBean.scheduledMethod1: 2 exiting at: Sat Mar 23 23:01:00 IST 2013

INFO: Server shutdown initiated
INFO: RAR7094: __xa_jdbc_ra shutdown successful.

INFO: JMXStartupService: Stopped JMXConnectorServer: service:jmx:rmi://MOHITGUPTA-PC:8686/jndi/rmi://MOHITGUPTA-PC:8686/jmxrmi
INFO: JMXStartupService and JMXConnectors have been shut down.
INFO: Shutdown procedure finished

As written in the explanation for the example,

scheduling collisions are resolved by GlassFish by creating a new instance of the stateless session bean and invoking the timeout callback method to be executed next on the new instance

Question 1-A:When it is decided to create a new instance ?
As seen in the output provided,the new instance is created when a new timeout callback method is to created. eg:

scheduledMethod1 is executed with a different instance after scheduledMethod2 is executed

Question 1-B:So,when will the next instance be created ?

I see that both the methods keep on executing with instance 2 and 3 in a random order.
Question 2:So,will these methods stop executing after the criteria in the cancelOverdue is met or there is any other way too ?

I have configured the hour to be hour = "6-23".
Question 3 :So, shouldn't the timer till run 23 hr ? ( I see it running past 23 too,Please see

"INFO: ScheduledStatelessSessionBean.scheduledMethod1: 3 entering at: Sat Mar 23 23:00:20 IST 2013"

in the output provided)

[Mohit G Gupta]

Please advise.

[Frits Walraven]

Hi Mohit,

Question 1-A:When it is decided to create a new instance ?

It has to use an idle instance for every timeout, so if all instances are serving a client (timeout), it will create a new one to serve the timout.

Question 2:So,will these methods stop executing after the criteria in the cancelOverdue is met or there is any other way too ?

No, they will just keep on expiring. Timers are also persisted, so even when you stop and start the server they will just keep on going to expire.

So, shouldn't the timer till run 23 hr ? ( I see it running past 23 too,Please see

Yes they should, but I guess the timer expired before 23 hrs and the log statement is only printed 15 seconds later (see waitSeconds(15);)

Regards,
Frits