Martijn Verburg wrote:Hi Andre and welcome to Javaranch!
It looks like the rescheduling is effectively storing the same trigger each time (which is therefore treated as a duplicate), is there some way you can uniquely create each trigger (or delete the old trigger before inserting the new one).
Hi Martijn,
Thanks for your reply!
My doubt is conceptual I think.
My scenario is: I need to run Quartz in a webapp in cluster using JobStoreTX.
Could I use the same trigger to reschedule the jobs when necessary or not?
Looking in the Quartz API I have found
Date rescheduleJob(String triggerName,
String groupName,
Trigger newTrigger)
throws SchedulerException
Remove (delete) the Trigger with the given name, and store the new given one - which must be associated with the same job (the new trigger must have the job name & group specified) - however, the new trigger need not have the same name as the old trigger.
I am trying to use that method without sucess..
Tks