Please clearify the behaviour of an container if an application exception is thrown during the execution of a timer callback method

[glassfishrobot]

Section 13.2.5.2 Timeout Callback Method Requirements of JSR 345: Enterprise JavaBeans, Version 3.2 contains the following requirement for a callback method:

Timeout callback methods must not throw application exceptions.

Although section 13.4 Container's Responsibilities does not specify how the container must behave if the timeout callback method throws an application exception.

The behaviour of the existing application servers like Glassfish, JBoss, and Geronimo differs in the way they handle callback methods those throw an application exception.

• Glassfish expunges the timer associated timer
• JBoss and Geronimo keep the timer and log the exception

Please specify the required behaviour of an application server in case of the occurence of an application exception during the execution of a timeout callback method. A standardised behaviour in this situation is required to write portable and reliable applications.

Affected Versions

[3.2, 3.3]

[glassfishrobot]

Reported by obfischer

[glassfishrobot]

This issue was imported from java.net JIRA EJB_SPEC-111