On p.394, table 23-24 of JSR 318, the container does not throw the system exception to the client from timeout callback methods in either CMT or BMT.
But on p.524, session 18.4.3 Timer Expiration and timeout callback method, it says
If the timer is a single-event timer, the container must cause the timer to no longer exist. If a javax.ejb.Timer interface method is subsequently invoked on the timer
after the completion of the timeout callback method, the container must throw the javax.ejb.NoSuchObjeectLocalException.
The Timer and TimerHandle methods can throw EJBException and etc. So, I believe the container should throw those exceptions to the client.
I think table 23-24 miss the fact that container throws the system exception.
This case is different from what we discussed in the previous post :https://coderanch.com/t/646025/java-EJB-SCBCD/certification/container-throw-EJBException-timeout-callback
In the previous post, the container throws the system exception when a transaction fails to commit.
But in this post, I think the EJBException (system exception) thrown from the instances of Timer or TimerHandle should be propagated to the container and the container will throw the EJBExceptions back the client.