When I set the "SchedulePeriod" property of the Scheduler MBean to 30 seconds, I think of it semantically as follows: Every 30 seconds, invoke this exposed MBean method with these parameters.
But under the current behavior, the semantics are as follows: After the current MBean method has completed, wait 30 seconds before the next invocation. So if I have an initial start time of 12:00:00, and a SchedulePeriod of 30 seconds, and the MBean invocation takes 5 seconds to complete, the second invocation will occur at 12:00:35. In a managed production environment, this leads to unpredictability of the scheduled processes. I have a patch to scheduler that invokes the Scheduled MBean in its own thread, so that the SchedulerMBean can immediately return to the TimerMBean, and allow the next invocation to be scheduled. This is still not a perfect solution, but IMHO it is much better than the current situation. Is this patch worth submitting, or do people prefer the current Scheduler behavior? Thanks, Corby _________________________________________________________ View thread online: http://main.jboss.org/thread.jsp?forum=66&thread=12516 _______________________________________________________________ Sponsored by: Looking for hip toys and fun scwag. There is no better place then the good friends at ThinkGeek. http://www.ThinkGeek.com/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
