It *can* use the Timer classes; it just doesn't. The danger in using Timer, of course, is resoruce starvation if the event being started restarts before the previous execution finishes.
On Fri, 25 Jan 2002, Justin Crosbie wrote: > Yes I have seen that, it is very bare-bones. It doesn't even use the Timer > classes. I need to know how to make this robust. > > Thanks, > Justin > > -----Original Message----- > From: Joseph B. Ottinger [mailto:[EMAIL PROTECTED]] > Sent: 25 January 2002 12:04 > To: Orion-Interest > Subject: Re: Job Scheduler pattern > > > The www.orionsupport.com site has a sample scheduler that can easily be > converted to do something like this. > > On Fri, 25 Jan 2002, Justin Crosbie wrote: > > > Hi, > > > > I'm not sure if I've asked this before, or if I should be asking on a > > general EJB list. > > > > I'd like to implement a job scheduler in J2EE. This would shcedule the > > execution of EJB methods at a specified time in the future. It would have > to > > be persistent, and jobsd would be rescheduled upon appserver restart. > > > > Is it as simple as using the Timer and TimerTask in java.util to implement > > an app that is started with the <client-module> tag? > > > > Does it matter as far as Orion goes whether I use a java.util.Timer as a > > daemon or not? > > > > What can I do if the app, or the Timer object dies at any stage? > > > > I've had problems where after some time something goes wrong I get a > strange > > Remote Exception, and the only solution is to restart the VM. What might > > cause this? > > > > Any opinions on this? How do I make this solution robust is what I am > > asking. > > > > Thanks for any help, > > Justin > > > > ----------------------------------------------------------- > Joseph B. Ottinger [EMAIL PROTECTED] > http://adjacency.org/ IT Consultant > > ----------------------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://adjacency.org/ IT Consultant
