Mar 6th, 2007, 11:03 AM
Using Quartz job scheduler to send e-mails
I am planning to use Quartz API to send the e-mails to the users. Users will receive emails on a daily or weekly basis based on their selection.
Can we use the same job here in both cases with different triggers associated with it, to send out e-mails based on user's selection?
Any further information in this regard is most welcome.
Mar 6th, 2007, 11:14 AM
Sounds like a reasonable thing to do. The Job should be exactly the same, the only difference is the execution times hence multiple triggers. Sounds ok IMHO.
Mar 6th, 2007, 03:18 PM
How is the job failure handled in case of Quartz jobs?
If the job does not run completely then how to make sure that it will restart from the correct position?
Mar 6th, 2007, 03:31 PM
It depends what you mean by job failure? An exception is thrown whilst excecuting the job? The job misfires?
Mar 6th, 2007, 03:39 PM
It could be any type of failure including system failure. Say a job is supposed to send out 200 messages and server went down in between and job could send only 100 messgaes.
After the system comes back up, how is this situation handled?
Mar 7th, 2007, 09:07 AM
Could anyone provide further information here?
Mar 7th, 2007, 10:37 AM
It shouldn't be any big issue with your this task. I had used Quartz with Spring without any development problems. You should be able to find a sample on the usage situation and learn how to program it right. It seems to be straightforward to me.
Mar 7th, 2007, 12:18 PM
If the job is persistent then there aren't any worries about the server going down. As you say your issue is more todo with how far through the execution list you have gotten before the server went down. I guess you'd have to store something so upon a restart you knew where to start from.