Using the RMI Registry

The RMI Registry needs to be run for clients to get access to the server object. You can choose to run the Registry from the command line using Java's rmiregistry command, or you can allow Quartz to start the Registry automatically. The choice is up to you, but if you don't have a preference, it's probably easiest to just allow Quartz to start it when it needs it.

If you do start the Registry from the command line, make sure the port that you start it on is the same as the port specified in the properties file. When starting from the command line, you change to the /bin directory and type this:


If you don't specify a port number, the default 1099 is used. This happens to be the default that Quartz uses as well.

If you don't want to run the Registry from the command line, Quartz will start it automatically if you have the correct value for the property org.quartz.scheduler.rmi.createRegistry. From Table 9.1, the property has several possible values:

  • false (never)
  • true (as_needed)
  • always

If you want Quartz to start the Registry, set the property to true or always.

Scheduling in the Enterprise

Getting Started with Quartz

Hello, Quartz

Scheduling Jobs

Cron Triggers and More

JobStores and Persistence

Implementing Quartz Listeners

Using Quartz Plug-Ins

Using Quartz Remotely

Using Quartz with J2EE

Clustering Quartz

Quartz Cookbook

Quartz and Web Applications

Using Quartz with Workflow

Appendix A. Quartz Configuration Reference

Quartz Job Scheduling Framework(c) Building Open Source Enterprise Applications
Quartz Job Scheduling Framework: Building Open Source Enterprise Applications
ISBN: 0131886703
EAN: 2147483647
Year: N/A
Pages: 148 © 2008-2020.
If you may any questions please contact us: