Unable to set trigger properties via QuartzTriggerHandle

[mrwaves]

Hi,

I got stuck due to the following problem:

I would like to set some trigger properties using the QuartzTriggerHandle. Unfortunately, this does not seem to have any affect on the qrtz_* tables in my MySQL Database.

For example, trying to set the misfired instruction to CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING fails. The value still has its default value CronTrigger.MISFIRE_INSTRUCTION_SMART_POLICY afterwards:

Trigger trigger = testClass.getQuartzTriggerHandle().getTrigger();
trigger.setMisfiredInstruction(CronTrigger.MISFIRE_INSTRUCTION_DO_NOTHING);

All other setters, I can call from the trigger-Object above have no effect at all as well.

For the moment, I update the quartz tables manually via JDBC to be able to set the appropriate misfire instruction.

For my quartz implementation, I used the quartz-example from the seam exmaple directory. Apart from the described behaviour above, it works quite well.

I am using Seam 2.2.0 GA and quartz 1.7.2.

Can someone explain why this does not work?

Thanks in advance
Thomas

[kapitanpetko]

Show your quartz.properties.

[mrwaves]

Hi Nikolay, thanks for your reply.

Here is my property file:

org.quartz.scheduler.instanceName = QuartzScheduler
org.quartz.scheduler.instanceId = 1
org.quartz.scheduler.rmi.export = false
org.quartz.scheduler.rmi.proxy = false

org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 5

org.quartz.jobStore.class = org.quartz.impl.jdbcjobstore.JobStoreTX
org.quartz.jobStore.driverDelegateClass = org.quartz.impl.jdbcjobstore.StdJDBCDelegate
org.quartz.jobStore.dataSource = testdb
org.quartz.jobStore.tablePrefix = qrtz_

org.quartz.dataSource.testdb.driver = com.mysql.jdbc.Driver
org.quartz.dataSource.testdb.URL = jdbc:mysql://localhost:3306/testdb
org.quartz.dataSource.testdb.user = testuser
org.quartz.dataSource.testdb.password = 12345678
org.quartz.dataSource.testdb.maxConnections = 10

[kapitanpetko]

Thomas Wellen wrote on Apr 05, 2010 22:18:


org.quartz.jobStore.class

• org.quartz.impl.jdbcjobstore.JobStoreTX

If you are note using JTS, that should be OK. Not a 100% sure about this, but to propagate your changes to the DB, you need to call scheduler.rescheduleJob(). I'm pretty sure the trigger itself does not do any DB access.

HTH

[mrwaves]

I am not able to get a reference to the scheduler since the getScheduler() method is declared as a private method inside the QuartTriggerHandle class. I can only access the trigger itself!

[kapitanpetko]

Yes, QuartzTriggerHandle is pretty useless. Use this:

Scheduler scheduler = QuartzDispatcher.instance().getScheduler();

HTH

[mrwaves]

Thanks a lot! That solved it.

I think, this should be mentioned in the docs/exmaples somewhere.

Cheers
Thomas