Ouch! It appears that a @Schedule can STILL become lost, even if you catch
(Exception e) in the method. When some JPA/EJB transaction is rolled back,
all hell breaks loose, and the @Schedule is lost. The method won't be called
again, EVER. This seems to be a serious bug in Glassfish. Or is it a
"feature"? Is there some easier way to have a scheduled idempotent task (say,
for surveillance), which is can be allowed to fail, but is guaranteed to be
called again at the next interval?
--
[Message sent by forum member 'tmpsa']
View Post: http://forums.java.net/node/706287