A few weeks ago we developed an EJB 3.0 TimerService to schedule some tasks on demand (when the user clicked a button, we would create the timer to perform some tasks). So far it's been working well, until today.
Yesterday we redeployed the EJB containing de TimerService to update some properties, and today no timers were fired, even though there were some created.
¿Is this normal? I mean, if you don't change the signature of the ejbTimeOut, shouldn't it launch as always after a redeploy?
Timers are persistent by default. When you restart server, redeploy application etc. probably if they were missed out, will timeout.
I have faced similar issues in the past. Therefore it's advisable to cancel all previous existing timers & then create new one afterwards.