| Category: | Bug report |
Priority: | Normal |
Status: | New |
| Project: | Severity: | Block |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
The trigger status error message comes up for any existing report once the Jasper 4.7 upgrade from 4.5.0 has been completed.
Reports dont run and if you try to edit the job then this error message is displayed after submitting last page of scheduled setup "Trigger's related Job's name cannot be null"
v4.7
1 Comment:
Jasper 4.5 seems to store a schedule name "TestScheduler" which can not be found by v4.7 in local java map. The following sql solved this issue for me (postgresql):
BEGIN;
ALTER TABLE qrtz_triggers
DROP CONSTRAINT qrtz_triggers_fkey;
ALTER TABLE qrtz_simple_triggers
DROP CONSTRAINT qrtz_simple_triggers_fkey;
ALTER TABLE qrtz_cron_triggers
DROP CONSTRAINT qrtz_cron_triggers_fkey;
UPDATE qrtz_triggers SET sched_name = 'quartzScheduler' WHERE sched_name = 'TestScheduler';
UPDATE qrtz_job_details SET sched_name = 'quartzScheduler' WHERE sched_name = 'TestScheduler';
UPDATE qrtz_simple_triggers SET sched_name = 'quartzScheduler' WHERE sched_name = 'TestScheduler';
UPDATE qrtz_cron_triggers SET sched_name = 'quartzScheduler' WHERE sched_name = 'TestScheduler';
ALTER TABLE qrtz_triggers
ADD CONSTRAINT qrtz_triggers_fkey FOREIGN KEY (sched_name, job_name, job_group)
REFERENCES qrtz_job_details (sched_name, job_name, job_group) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION;
ALTER TABLE qrtz_simple_triggers
ADD CONSTRAINT qrtz_simple_triggers_fkey FOREIGN KEY (sched_name, trigger_name, trigger_group)
REFERENCES qrtz_triggers (sched_name, trigger_name, trigger_group) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION;
ALTER TABLE qrtz_cron_triggers
ADD CONSTRAINT qrtz_cron_triggers_fkey FOREIGN KEY (sched_name, trigger_name, trigger_group)
REFERENCES qrtz_triggers (sched_name, trigger_name, trigger_group) MATCH SIMPLE
ON UPDATE NO ACTION ON DELETE NO ACTION;
COMMIT;