Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.

Topic-icon Question ETL run does not start at scheduled time

More
19 Sep 2019 09:20 #1 by hyesane
hyesane created the topic: ETL run does not start at scheduled time
Hi Team,

We have scheduled stambia cron job to run at 2 AM everyday but all of sudden it stopped executing itself at 2 AM and we have found below runtime log information.

[INFO] 19 Sep 02:01:16.411 AM QuartzScheduler_RUNTIME_H2_STD-RUNTIME_H2_STD_MisfireHandler [org.quartz.impl.jdbcjobstore.JobStoreTX]
Handling 1 trigger(s) that missed their scheduled fire-time.

Please explain the error and let us know hot to correct it so that stambia cron start executing etl itself by 2 AM.
More
19 Sep 2019 11:02 #2 by Thomas BLETON
Thomas BLETON replied the topic: ETL run does not start at scheduled time
Hi,
This message informs that the Scheduler could not start the job, usually it happens when there is another job already running for the same "job name" or delivery name, depending on how the schedules were defined.
This is the default standard behavior of the scheduler.
In your case, I would:
=> double check the other schedules to see if their executions may overlap
=> set a different jobname to the schedules that you want to run in parallel, otherwise they won't start.

I hope this helps