Configure Scheduler JMX Settings

Export the Quartz Scheduler to a local MBean server so a client create a remote proxy Scheduler instance.

JMX Scheduler Server Properties

Property Name Required Default Value
org.quartz.scheduler.jmx.export no false
org.quartz.scheduler.jmx.objectName no quartz:type=QuartzScheduler,name=<instanceName>,instance=<instanceId>

org.quartz.scheduler.jmx.export
Whether to export the Quartz Scheduler to the local MBean server. Defaults to false.

org.quartz.scheduler.jmx.objectName
The object name under which the Scheduler is registered with the local MBean Server. Default domain is 'quartz' with 'type' of 'QuartzScheduler', 'name' of 'org.quartz.scheduler.instanceName', and 'instance' of 'org.quartz.scheduler.instanceId'. Note that if 'org.quartz.scheduler.instanceId' is AUTO, the automatically generated instanceId will be used, not the 'AUTO' string.


JMX Scheduler Client Properties

Property Name Required Default Value
org.quartz.scheduler.jmx.proxy no false
org.quartz.scheduler.jmx.proxy.class yes
org.quartz.scheduler.jmx.objectName no quartz:type=QuartzScheduler,name=<instanceName>,instance=<instanceId>

org.quartz.scheduler.jmx.objectName
The object name under which the Scheduler is registered with the remote MBean Server. Default domain is 'quartz' with 'type' of 'QuartzScheduler', 'name' of 'org.quartz.scheduler.instanceName', and 'instance' of 'org.quartz.scheduler.instanceId'. Note that if 'org.quartz.scheduler.instanceId' is AUTO, then 'NON_CLUSTERED' will be used, not the 'AUTO' string.

org.quartz.scheduler.jmx.proxy
Whether to create a Scheduler instance that is a proxy to a Scheduler instance that was exported on a remote MBean server.

org.quartz.scheduler.jmx.proxy.class
A org.quartz.impl.RemoteMBeanScheduler subclass that knows how to connect to your application specfic remote MBean server. You can set properties of this class with properties of the form: 'org.quartz.scheduler.jmx.proxy.propertyName' A JBoss 4.0+ specfic implementation is provided in class 'org.quartz.ee.jmx.jboss.JBoss4RMIRemoteMBeanScheduler' (see javadoc for details).

It does not make sense to specify a 'true' value for both 'org.quartz.scheduler.jmx.export' and 'org.quartz.scheduler.jmx.proxy' in the same config file - if you do, the 'export' option will be ignored. A value of 'false' for both 'export' and 'proxy' properties is of course valid, if you're not using Quartz via JMX.