config/quartz.properties
author Antonio Moreno <antonio.moreno@openbravo.com>
Mon, 13 Feb 2012 17:58:29 +0100
changeset 15483 f52dabf2bdc4
parent 1867 a2cb0934dfb0
permissions -rw-r--r--
Fixed issue 16868. ComponentProviders will be matched with modules via the javapackage smartly:
- A class will be matched to a module if its javapackage starts with the javapackage of the module (we no longer require the matching to be exact).
- If more than one module matches, the one with the longest Javapackage will be picked. This is to resolve situations in which, for example, both org.openbravo and org.openbravo.client.kernel match.
anthony@1867
     1
## Quartz properties
anthony@1867
     2
org.quartz.scheduler.instanceName = DefaultQuartzScheduler
anthony@1867
     3
org.quartz.scheduler.rmi.export = false
anthony@1867
     4
org.quartz.scheduler.rmi.proxy = false
anthony@1867
     5
org.quartz.scheduler.wrapJobExecutionInUserTransaction = false
anthony@1867
     6
anthony@1867
     7
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
anthony@1867
     8
org.quartz.threadPool.threadCount = 10
anthony@1867
     9
org.quartz.threadPool.threadPriority = 5
anthony@1867
    10
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread = true
anthony@1867
    11
anthony@1867
    12
org.quartz.jobStore.misfireThreshold = 60000
anthony@1867
    13
anthony@1867
    14
org.quartz.jobStore.class = org.quartz.simpl.RAMJobStore