detecting delayed timer after server restart

[Jonh Smith]

The following is taken from the ejb 3.0 spec:

"Timers are persistent objects. In the event of a container crash, any single-event timers that have expired
during the intervening time before container restart must cause the timeout callback method to be
invoked upon restart. Any interval timers that have expired during the intervening time must cause the
timeout callback method to be invoked at least once upon restart."

I have a single-action timer and in case of a server crash that takes long enough so that the timer becomes outdated, I need to make sure that the timeout handling is done in a different way. I was hoping that the getTimeRemaining method would return a negative value in this case but apparently google search indicates otherwise. There seems to be nothing in the standard addressing my need. Is there any easy way to detect a delayed timer due to server restart in the bean's timeout method?

thanks

[Devaka Cooray]

"new forjavaranch", please check your private messages regarding an important administrative matter.