I'm with Larry. Cron rocks. The only problem you should have in mind: if your job needs more then the time between the jobs, you've lost. We had actually this problem, and it killed the db, because (2 years after initially written) the script lasted more then 24 hours, and after a week 5 instances of it runned, blocking each other and producing a load of 10 on the machine.
So simply add a check "am I already running" to your code, and it will be fine :-) regards Leon On Wed, 2005-07-13 at 21:49 -0600, Larry Meadors wrote: > I would probably go the route of the .sh file. > > At the risk of starting a big flame war, cron is solid as a rock, and > all of the memory used by your app will be freed up when the JVM > exits. Why make it more complex by adding quartz or tomcat to the mix > if you do not have to. > > Simple is *almost* always better. > > Larry > > > On 7/13/05, Richard Reyes <[EMAIL PROTECTED]> wrote: > > Hello Guys, > > > > I need your suggestions. I have a task to create an application to > > sync records between 2 Oracle 10g database. Not the whole records of > > the database though, just the now and then transactional updates. > > Access to the db's would be both via web services. I think I have an > > option to do this like > > - a simple java application executed via .sh file > > - a java application running as a daemon on a unix box > > > > But I really am not sure which better path I should take. Any > > suggestions would be very much appreciated. > > > > Thanks > > Richard > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
