Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

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

More
19 Sep 2019 09:20 #1 by hyesane
ETL run does not start at scheduled time was created by hyesane
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
Replied by Thomas BLETON on 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