Re: [JBoss-dev] Jboss2.4.4 scheduler
Hi Yes, this was a problem and was fixed in 2.4.5 as Scott already said. But you fix won't work either because you added a period which is not correct because this is the initial call (one time call) only to be there to cause one notification. Later one this will be used to recalculate the Schedule. Please note that the entire way the Scheduler works is redesigned and not it works differently. Thus the Scheduler will calculate the next schedule in the future with respect to the number of occurences. Therefore you can bounce the server and pick up where you left. Andy - Original Message - From: "kv" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 12:36 AM Subject: [JBoss-dev] Jboss2.4.4 scheduler > Hi team, > I'm not quite sure if this is the right place for reporting this sort of thing, but here it is: > The class org.jboos.util.Scheduler has the following invocation of the Timer mbean addNotification method while there is no such method with that signature: > This call is made when the value of the schedule start date is more than 'time-now'. > line 290: // Add an initial call > mActualSchedule = ( (Integer) getServer().invoke( >mTimer, >"addNotification", >new Object[] >{ > "Schedule", > "Scheduler Notification", > mStartDate, >}, >new String[] >{ > String.class.getName(), > String.class.getName(), > Date.class.getName(), >} >) ).intValue(); > } > Changing the above to the following fixed the problem. > // Add an initial call > mActualSchedule = ( (Integer) getServer().invoke( >mTimer, >"addNotification", >new Object[] >{ > "Schedule", > "Scheduler Notification", > null, > mStartDate, > new Long( mActualSchedulePeriod ) >}, >new String[] >{ > String.class.getName(), > String.class.getName(), > Object.class.getName(), > Date.class.getName(), > Long.TYPE.getName() >} >) ).intValue(); > } > Thanks for jboss, > and remember we love you. > * * * > > View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=15979 > > ___ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > ___ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Jboss2.4.4 scheduler
There were fixes to the scheduler in 2.4.5 so get the latest release which is 2.4.6. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: "kv" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 20, 2002 12:36 AM Subject: [JBoss-dev] Jboss2.4.4 scheduler > Hi team, > I'm not quite sure if this is the right place for reporting this sort of thing, but here it is: > The class org.jboos.util.Scheduler has the following invocation of the Timer mbean addNotification method while there is no such method with that signature: > This call is made when the value of the schedule start date is more than 'time-now'. > line 290: // Add an initial call > mActualSchedule = ( (Integer) getServer().invoke( >mTimer, >"addNotification", >new Object[] >{ > "Schedule", > "Scheduler Notification", > mStartDate, >}, >new String[] >{ > String.class.getName(), > String.class.getName(), > Date.class.getName(), >} >) ).intValue(); > } > Changing the above to the following fixed the problem. > // Add an initial call > mActualSchedule = ( (Integer) getServer().invoke( >mTimer, >"addNotification", >new Object[] >{ > "Schedule", > "Scheduler Notification", > null, > mStartDate, > new Long( mActualSchedulePeriod ) >}, >new String[] >{ > String.class.getName(), > String.class.getName(), > Object.class.getName(), > Date.class.getName(), > Long.TYPE.getName() >} >) ).intValue(); > } > Thanks for jboss, > and remember we love you. > * * * > > View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=15979 > > ___ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > ___ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] Jboss2.4.4 scheduler
Hi team, I'm not quite sure if this is the right place for reporting this sort of thing, but here it is: The class org.jboos.util.Scheduler has the following invocation of the Timer mbean addNotification method while there is no such method with that signature: This call is made when the value of the schedule start date is more than 'time-now'. line 290: // Add an initial call mActualSchedule = ( (Integer) getServer().invoke( mTimer, "addNotification", new Object[] { "Schedule", "Scheduler Notification", mStartDate, }, new String[] { String.class.getName(), String.class.getName(), Date.class.getName(), } ) ).intValue(); } Changing the above to the following fixed the problem. // Add an initial call mActualSchedule = ( (Integer) getServer().invoke( mTimer, "addNotification", new Object[] { "Schedule", "Scheduler Notification", null, mStartDate, new Long( mActualSchedulePeriod ) }, new String[] { String.class.getName(), String.class.getName(), Object.class.getName(), Date.class.getName(), Long.TYPE.getName() } ) ).intValue(); } Thanks for jboss, and remember we love you. * * * View thread online: http://jboss.org/forums/thread.jsp?forum=66&thread=15979 ___ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development