Terracotta Discussion Forums

Hi,

I want to specify quartz' properties at startup.

More precisely, I'd like to define quartz properties on application specific basis (each application has its db connection user, that connection user should contain also the timer tables). I do not wat JBoss start up with a generic quartz configuration at all; applications should provide it.

The first step towards this: where is the file that defines the quartz.properties for JBoss? I modified quartz.properties contained in /common/lib/quartz.jar, but evidently this is not used, as the console confirms:

Code:

11:26:55,903 INFO  [SchedulerSignalerImpl] Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
 11:26:55,904 INFO  [QuartzScheduler] Quartz Scheduler v.1.8.3 created.
 11:26:55,906 INFO  [RAMJobStore] RAMJobStore initialized.
 11:26:55,909 INFO  [QuartzScheduler] Scheduler meta-data: Quartz Scheduler (v1.8.3) 'JBossQuartzScheduler' with instanceId 'NON_CLUSTERED'
   Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
   NOT STARTED.
   Currently in standby mode.
   Number of jobs executed: 0
   Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
   Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.
 
 11:26:55,909 INFO  [StdSchedulerFactory] Quartz scheduler 'JBossQuartzScheduler' initialized from an externally opened InputStream.
 11:26:55,909 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.8.3

I'm following the Quartz documentation (http://quartz-scheduler.org/documentation/quartz-1.x/configuration/), but I'm confused about if the .properties should be used, rather than a service xml, like this one here (http://quartz-scheduler.org/api/1.8.5/org/quartz/ee/jmx/jboss/doc-files/quartz-service.xml) for instance.

Thanks,

~pasquale

Hello,

More precisely, I'd like to define quartz properties on application specific basis (each application has its db connection user, that connection user should contain also the timer tables). I do not wat JBoss start up with a generic quartz configuration at all; applications should provide it.

you should use one quartz.properties per application : put each quartz.properties file in each app's WEB-INF/classes folder (see http://quartz-scheduler.org/documentation/quartz-2.x/quick-start)

you should use one quartz.properties per application : put each quartz.properties file in each app's WEB-INF/classes folder (see http://quartz-scheduler.org/documentation/quartz-2.x/quick-start)

That's exactly what I'd like to achieve :)
Sticking to MVC and standards, the quartz configuration should go into META-INF of the *-ejb.jar, which stands for Model. View and Control go into WAR - although these separations are not strict (you can deploy EJBs in WAR as well).

Is the documentation you've linked to also valid for Quartz 1.8.3, which is shipped with JBoss 6 ?

Hello,
using quartz 1.8.3, you should rather read this documentation :
http://quartz-scheduler.org/documentation/quartz-1.x/quick-start
Anthony