Quartz1.6.4 - how to maintain state after system/application restart

[jeff rusty]

Hi ,

In my web application i have a requirement to create jobs dynamically and add it to the scheduler all works fine except when i restart my application or system.
Can somebody guide me with the ways to maintain the JoB state in QUARTZ after system restart. I know that it can be done with JDBC store but i dont wan to use database since it can cause performance issue. Is there is a way where i can use the Job.xml to be updated after creating every job and loading it.
I am using SPRING with quartz zo is there is any way by which SPRING can do the updation of the XML and maintain the state.

please help

Thanks

[Martijn Verburg]

Not that's I'm aware of, we use a JDBC Store (performance is OK), but found that the SQL generated for Sybase isn't quite correct, so sometimes on server restart it wasn't picking up the stored jobs, we're still investigating that one

[jeff rusty]

thanks for your reply..

are you using spring? if so can you please let me know how to configure it for persistent jobs.

Thanks

[Martijn Verburg]

Hi Jeff,

My colleague (also a Jeff) passed me our current config:

Depending on what flavour of database he is using, the table creation script is in the quartz download, but here is the Sybase one attached. Quartz has a good reference page in its later docs, but the properties are somewhat scattered.

Note the XA resource stuff is commented out for now and we had to use the MS SQL Server driver as you can see below...

Our Spring config entries:-

    <!-- Create a Quartz scheduler and associate jobFactory and triggers -->
    <bean id="scheduler" class="org.springframework.scheduling.quartz.SchedulerFactoryBean">
        <property name="quartzProperties" ref="quartzProperties"/>
        <!--property name="dataSource" ref="xaDataSource"/-->
        <property name="jobFactory" ref="ikasanJobFactory"/>
        <property name="triggers">
            <list>
                <ref bean="perSecurityPolling_schedule" />
            </list>
        </property>
    </bean>

    <bean id="quartzProperties"
         class="org.springframework.beans.factory.config.PropertiesFactoryBean">
      <property name="properties">
        <props>
          <!--prop key="org.quartz.jobStore.class">org.quartz.simpl.RAMJobStore</prop-->
          <prop key="org.quartz.jobStore.class">org.quartz.impl.jdbcjobstore.JobStoreCMT</prop>
          <prop key="org.quartz.jobStore.driverDelegateClass">org.quartz.impl.jdbcjobstore.MSSQLDelegate</prop>
          <prop key="org.quartz.jobStore.tablePrefix">QRTZ_</prop>
          <prop key="org.quartz.jobStore.selectWithLockSQL">SELECT 1 UPDATE QRTZ_LOCKS SET LOCK_NAME=LOCK_NAME WHERE LOCK_NAME = ?</prop>
          <prop key="org.quartz.jobStore.txIsolationLevelSerializable">true</prop>
          <!--prop key="org.quartz.jobStore.dataSource">java:/ikasan/framework/defaultXA/xads</prop-->
          <prop key="org.quartz.jobStore.useProperties">true</prop>
        </props>
      </property>
    </bean>

[jeff rusty]

hi Martijn,

Thank you for your quick reponse. But i still didnt get how this will help when i create jobs dynamically as i am new to spring and quartz.

what goes in your 'ikasanJobFactory' 'and perSecurityPolling_schedule' ?

Thanks,
jeff

[Martijn Verburg]

The ikasanJobFactory is a bean that instantiates a JobFactory, in fact we use a SimpleJobFactory.

The other item is a trigger bean again that's defined in the Spring config, see Trigger We use a CronTrigger IIRC.