Joseph, Very cool. How do you stop a client-module that auto-started and then restart it?
Say you deployed the app (which also has ejb and web modules) and later wanted to add another task to the scheduler. Can you start and stop the java client module, so that it would reload the properties file, without affecting the web module? I might have users logged in to the website and I wouldn't want to redeploy everthing and messup any current sessions. Thanks, Paul -----Original Message----- From: Joseph B. Ottinger [mailto:[EMAIL PROTECTED]] Sent: Friday, January 25, 2002 4:04 AM 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
