> > For regular tasks of the sort you describe, especially things like > > sending out regular emails, backing up systems, and other maintenance > > tasks, you may want to consider using cron on a unix machine instead. > > Yup, lots of CRON-style functionality already exists, so no reason to > invent your own scheduler. Independent of that decision, you may gain > some reliability by running scheduled tasks in a separate process from > the webapp. If people depend on receiving those emails in a certain > timeframe, you don't want a webapp failure to get in the way.
It's all good advice and I have used cron before so it should not be hard. However, there is one problem and that is that I need to open up a Derby database from the cronjob, but as the database is already open in the webapp, it is locked and cannot be opened until the webapp is closed. So I will go for using a Timer, for now. The scheduling is not very critical (It's more like "nice to have" and I could even call the appropriate function manually once per week if needed) and restarting the app if it becomes unstable in any way is no biggy either. Thanks for all the tips! /Mathias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
