Difference between revisions of "Monitoring Cluster-Enabled Quartz Instances"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 3: | Line 3: | ||
;Preparation: | ;Preparation: | ||
:* Add these lines to the <tt>quartz.properties</tt> file: | :* Add these lines to the <tt>quartz.properties</tt> file: | ||
<syntaxhighlight lang="java" enclose="div"> | ::<syntaxhighlight lang="java" enclose="div"> | ||
org.quartz.jobStore.isClustered = true | org.quartz.jobStore.isClustered = true | ||
org.quartz.jobStore.clusterCheckinInterval = 20000 | org.quartz.jobStore.clusterCheckinInterval = 20000 | ||
Revision as of 00:41, 19 July 2011
Monitoring Cluster--Enabled Quartz Instances
- Preparation
-
- Add these lines to the quartz.properties file:
- <syntaxhighlight lang="java" enclose="div">
org.quartz.jobStore.isClustered = true org.quartz.jobStore.clusterCheckinInterval = 20000 </syntaxhighlight>
- Monitoring
-
- Download the monitor_quartz.pl (Perl) script from the downloads area, and run it on your server.
- How it Works
- The lines in the properties file cause quartz to put an entry into the relationals.QRTZ_SCHEDULER_STATE table in the database. The script checks the timestamp to verify that the last stamp was within 5 minutes. (Quartz should be running once a minute. If it hasn't run in five minutes, it is considered to be down.)