Comments on: Configuring Quartz Scheduler to Run in Clustered Environment https://myshittycode.com/2013/09/26/configuring-quartz-scheduler-to-run-in-clustered-environment/ Embracing the Messiness in Search of Epic Solutions Fri, 06 Jan 2023 17:20:33 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: yardem https://myshittycode.com/2013/09/26/configuring-quartz-scheduler-to-run-in-clustered-environment/#comment-11 Fri, 07 Aug 2015 15:42:42 +0000 http://myshittycode.com/?p=73#comment-11 thank you, it works very good for me

]]> By: Choon-Chern Lim https://myshittycode.com/2013/09/26/configuring-quartz-scheduler-to-run-in-clustered-environment/#comment-10 Fri, 27 Sep 2013 19:15:47 +0000 http://myshittycode.com/?p=73#comment-10 In reply to jthiesse19.

The database manages the semaphore to ensure only one running node is executing the triggerred job. If you run this SQL query select * from dbo.QRTZ_TRIGGERS, you will see which job is currently running, when it will run again, etc.

]]> By: jthiesse19 https://myshittycode.com/2013/09/26/configuring-quartz-scheduler-to-run-in-clustered-environment/#comment-9 Fri, 27 Sep 2013 15:06:19 +0000 http://myshittycode.com/?p=73#comment-9 Where is the magic allowing for multiple concurrently running nodes to not collide?

]]>