-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding existing triggers back to scheduler after restart #1
Comments
Hey Muruga, the job store already enhances 2 mechanisms for releasing As i understand, you are talking about the first mechanism. Did you On 9/8/2014 8:20 PM, Muruga Chinnananchi wrote:
Signature Template Matan Kehat | Channel Integration Lead Mobile (IL): +972 (54) 549-5514 Blog https://www.redislabs.com/blog/ | Twitter |
Thanks Matan, i configured to use instanceIdFilePath with one quartz scheduler running, here is my use case:
i can list the jobs after restart, but it is not getting triggered. i will try out "releaseTriggersInterval". |
Thanks so much for open souring the redis JobStore. i am planning to use this for a project, i did little bit of testing and realized that on scheduler restart, the existing triggers are not getting added back to scheduler. looks like we need something like org.quartz.impl.jdbcjobstore.JobStoreSupport.MisfireHandler for redis job store.
The text was updated successfully, but these errors were encountered: