recurring timer and app re-start issue

[ajay662]

Using ej3 timer service, I am creating a recurring hourly timer. Its working fine if I leave my application running, i.e. I get the initial timer callback as specified and then hourly from then on.

However, after getting my initial timer callback, if I re-deploy my app or re-start jboss before the next due hourly callback time, I do get called back right away. I was expecting that I should be called back only when my next hourly callback is due, since initial callback had already been delivered.

Is this a bug or as per specs?

[wolfc]

Timers are persisted on undeployment and restored upon deployment.
http://jira.jboss.com/jira/browse/EJBTHREE-630

[ajay662]

Exactly. So the persisted state should be that initial timer has been delivered. And hence when I re-start jboss initial timer should not be re-delivered.

[wolfc]

How did you create the recurring timer?
Do you check whether there is already a timer active?

[ajay662]

I created the timer on a freshly installed jboss instance (so no prior timers) using the code below:

timer = messageDrivenCtx.getTimerService().createTimer(
 job.getFirstSchedTime(), job.getRecurringInterval(), job);

Here recurring-interval is 1 hour (in milliseconds). After I got my first timer callback I restarted the server and saw the timer calback right away on restart. Multiple restarts of the server showed the same behavior.

This is 100% reproducible.

[ajay662]

Nobody else is experiencing this??

This is a major problem. I have a bunch of tasks scheduled to do nightly maintenance on my devices at 1pm every night. So I am using a recurring timer to schedule these. Everything works as expected if I keep my application running. But if have to re-start my application for any reason, all those timers get fired right away..