Hi, Jonh
On 7/22/08, John Sanabria <john.sanabria@...> wrote:
Hi Sergey,
I assume that "I run multiple instances of it with different parameters for every instance at the same time" means that you created triggers manually and then scheduled jobs with Scheduler.scheduleJob(Trigger).
Yes, you're right. I have a term misconception.
In this case you can give your triggers unique names and then delete them using Scheduler.unscheduleJob(String triggerName, String triggerGroup)
OK, however, if my job is running and it doesn't stop because an I/O delay, the "unscheduleJob" method stops the current job execution? I read in the API that this method remove the trigger, but isn't clear what happen with running jobs associated with the unscheduled trigger?
I remark that, because I want to stop/interrupt the running job but keep the trigger for the future.
Ah, sorry, I misunderstood. I'm not sure if the Quartz itself has such a feature, but I'll investigate further and post about results.
Cheers
--
Sergey Nebolsin
Principal Software Engineer, Prophotos.ru
