Ask on the EJB3 forum, Seam just delgates to EJB3 here.
1) Are you using HSQLDB (default for JBoss)?
2) Was that select executed before or after the restart of JBoss? Check to see if there are any additional rows after the restart, I was seeing some weird things with HSQLDB and EJB3 timers when I was using them recently.
3) If you are using HSQLDB, don't use it in prod.
4) And keep in mind that EJB3 timers are not clusterable (at least not with JBoss, but I don't think it's part of JSR220). Quartz timers are clusterable.
2. You mean the select of the rows from the TIMERS table? After.
3. I'm not :)
4. I don't need clustering in this instance, but of course, if Quartz doesn't have this issue, then I might have to investigate it.
post this on the JBoss/EJB3 forum, sounds erroneous/abnormal to me...