Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. clustering (failover) feature is not available,
  2. tasks do not "know" when they run last time, so e.g. interval-based loosely-coupled tasks will be started immediately, even if their expected start time has not come yet; or misfired cron-based tasks would not start (even if configured to do so), because the information on the misfire event would not be present. This may cause for example reconciliation task(s) to be started immediately after midPoint is started.

More advanced installations could use JDBC-based Quartz job store - a store that will remember task scheduling information.