Did you ever get an answer to this question? If so, please explain how you were able to address this issue - I'm very interested. Thanks!
I didn't find an answer to this. My interpretation of the specs suggest that the timerService.getTimers() call has to be in the enterprise bean that creates the timer.
In seams case it the TimerServiceDispatcher class which is part of org.jboss.seam.async package.
In the end I just use the jmx-console to view the timers online.
The way we did it was to save the TimerHandler in the db as a Lob,
@Lob private TimerHandle timerHandle;
You get the handler from timer.getHandle();
You can then retrieve it and use it at a later stage.
Any one of you found out how to check, display and cancel relevant timers?
Problem with Pieter's approach is that timer handle cannot be trusted after server restart. I keep getting
NoSuchObjectLocalExceptionwhen I try to cancel a scheduled timer through timer handle after server restart. Apparently, on server restart, JBoss persists all the timers again and thereby changing the timer id. Since, timer id is changed, the timer handle cannot locate the timer.