calendar recurrence not firing at specified time

[contentengineer]

Wonder if anybody can help/suggest fix.

 

JasperServer with a number of reports scheduled to run on simple and calendar recurrence.

 

Simple recurrence is fine for daily repetition and repeats every day at "start time" of job (for example 21:15), as programmed.

 

We've modified some schedules to use calendar recurrence to enable daily repetition on work days (Mon thro' Fri). Even though we've set minutes (10) and hours (21), plus weekday Mon-Fri; the jobs repeat whenever the day changes (at 00:00) not at the specified time (i.e. 21:10)

 

Is there an error in the logic, or do we need to reset the start time/date to be in the future?

[contentengineer]

Running 1.2 with MySQL.

Checked database for jobs

 

jireportjobcalendartrigger j

id=52 minutes=15 hours=21 days_type=2 week_days=2,3,4,5,6 month_days= months=1,2,3,4,5,6,7,8,9,10,11,12

 

jireportjob;

id=5 version=8 username,label,description... job_trigger=52 content_destination=5 mail_recipient=8

 

jireportjobtrigger;

id=52 version=2 timezone=Europe/London start_type=2 start_date=2007-04-25 21:10:00 end_date=null

 

BUT noticing quartz entries:

 

qrtz_cron_triggers;

trigger_name= trigger_52_0 trigger_group=ReportJobs cron_expression 0 0 0 ? * 2,3,4,5,6 time_zone_id=Europe/London

 

 

Timezone Europe/London

Locale en

DS Timezone Europe/GMT

 

Is there a problem with Quartz being populated with the correct time/date?

[contentengineer]

In aim to fault find, went back to scheduling GUI; switch job from calendar->simple->calendar; re-entered minutes/hours and weekdays/ saved. Checked database and CRON_EXPRESSION now has the desired entry.

 

Need to test.

 

Suspect bug in calendar occurence action when changing minutes/hours; that it is not recreating the CRON_EXPRESSION column in the qrtz_cron_triggers table.

[lucianc]

This might be caused by a bug in JS 1.2.0 (which was fixed in 1.2.1).

 

The bug causes the scheduling service not to detect that the trigger has been updated, and hence not to recreate the Quartz trigger. This might explain why the Quartz trigger attributes are not in sync with the JS metadata.

 

You can find more details and a patch for 1.2.0 here. Note that if you intend to test the patch, you would need to change something in the job trigger and save the job so that the Quartz trigger gets recreated.

 

Regards,

Lucian

[contentengineer]

Thanks for the pointers and patch. We've updated the XML file, and put the jar file in the lib directory, restarted jasperserver etc etc.

 

When we change an entry in the calendar reoccurrence (i.e. minutes) this does not get reflected in the qrtz_cron_triggers table in MySQL; and next exectute time is showing as the old values.

 

However jireportjobcalendartrigger has the correct (updated meta data).

 

No errors in any logs.

 

Am I missing something?

[lucianc]

Have you seen the part about editing applicationContext-report-scheduling.xml in the discussion I mentioned? The patch needs this change in order to become effective.

[contentengineer]

Just checked. Had updated XML as described, however old file has been retained with XML extension rather than "OLD" and therefore it was getting confused.

 

Changed extension on original file, and restarted ... all working ok - passes thro' meta data to Quartz OK.

 

THANK YOU FOR YOUR ASSISTANCE.