Export to GitHub

myschedule - issue #96

Job & Trigger are left when DB scheduler is deleted


Posted on Aug 27, 2012 by Massive Kangaroo

What steps will reproduce the problem? 1. Create DB scheduler 2. Create Job / Trigger to run 3. Delete DB scheduler

What is the expected output? What do you see instead? 1. Job & Trigger should be deleted as well

Please use labels and text to provide additional information.

Comment #1

Posted on Aug 27, 2012 by Massive Dog

Hello Magicboo,

What you described is expected, not a bug.

If you were to create a database scheduler configuration, then all job and trigger data are persist into database. When you delete the "DB Scheduler", you simple deleting the quartz configuration, not the data in the database. It's user responsible to delete the repeating jobs/triggers from the scheduler if you intend not to use it anymore.

Comment #2

Posted on Aug 27, 2012 by Massive Dog

(No comment was entered for this change.)

Comment #3

Posted on Aug 30, 2012 by Massive Kangaroo

Got it! Thanks for your reply... But...I don't know how to delete or close this issue!

Comment #4

Posted on Aug 31, 2012 by Massive Dog

No problem. I have tag this issue as "Question" and I will clean them up once in a while.

Comment #5

Posted on Aug 31, 2012 by Massive Dog

(No comment was entered for this change.)

Status: Answered

Labels:
Type-Question Priority-Medium