Hi,
I finally got chance to look at this.
You are correct with your analysis of the Timer service and the
NotificationBroadcaster.
But I don't think this affects the Scheduler. It only registers
one listener with the timer.
If you want a second MBean, you create a second scheduler which
in turn c
Hi Corby
Thanx for looking into it. Will check with Juha / Adrian to see what they
think.
> My patch addresses this problem without altering
NotificationBroadcastSupport. The SchedulerMBean receives the synchronous
notification, creates a new Thread to actually invoke the MBean, and returns
the
I looked at the new JBossMX stuff; Juha's rewrite of the Timer has fixed part of the
problem. He does a much better job than Sun's Timer of determining what the next call
time should be, and so in the example I gave he will attempt to execute the second
MBean invocation at 12:00:30 rather than
on 09-04-2 20.36, cepage at [EMAIL PROTECTED] wrote:
> t invocation to be scheduled. This is still not a perfect solution, but IMHO
> it is much better than the current situation.
Please submit this as a patch at :
http://sourceforge.net/tracker/?group_id=22866&atid=376687
This way all contrib
this problem is fixed in JBossMX.
Have fun - Andy
- Original Message -
From: "cepage" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 11:36 AM
Subject: [JBoss-dev] Scheduled MBeans (Suggested Patch)
> When I set the "SchedulePeriod&qu
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 compl
