Monitoring Cluster-Enabled Quartz Instances
From AgileApps Support Wiki
Revision as of 17:53, 19 July 2011 by imported>Aeric
Monitoring Cluster--Enabled Quartz Instances
- Verify that these lines are in the quartz.properties file. (They are present in new installations, but are not automatically added during upgrades.)
- <syntaxhighlight lang="perl" enclose="div">
org.quartz.scheduler.instanceId = AUTO ... org.quartz.jobStore.misfireThreshold = 60000 ... org.quartz.jobStore.isClustered = true org.quartz.jobStore.clusterCheckinInterval = 20000 </syntaxhighlight>
- Download the monitor_quartz.pl (Perl) script from the platform downloads area.
- Modify these values for your installation:
- $hostname - Server name
- $mysql_username - Database user name.
- $mysql_password - Database password.
- $mysql_host - Name of server the database is running on.
- $config_file - Absolute path to tomcat/webapps/networking/WEB-INF/web.xml
- $recipients - Comma-separated list of email addresses who will receive email status messages
- ... - ...
- Run the script 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.)