I have a simple JEE timer example I'm working with, and the actual code simply blows out with a NullPointerException. This is by design, as I'm testing the error handling.
Anyway, it seems the the JEE Timer Service within GF v1b14 calls the @Timeout method twice if the first one blows up.
Is this a feature or a bug? Does it depend on what kind of exception is being thrown?
Here's the message in the log:
EJB5119:Expunging timer ['4@@1180473128971@@server@@domain1' 'TimedObject = JobSessionBean' 'Application = core' 'BEING_DELIVERED' 'SINGLE-ACTION' 'Container ID = 77363560038072322' 'Tue May 29 14:31:29 PDT 2007' '0' ] after [2] failed deliveries
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=219344