After upgrading to jira 7 results in " JIRA-Bootstrap FATAL" for the scheduler

Issue #155 on hold
Jóhann B. Guðmundsson created an issue

After upgrading to jira 7 and the plugin fails with fatal error "he values for day-of-week must be from 1 to 7."

2016-10-06 17:09:23,753 JIRA-Bootstrap FATAL [p.c.t.thescheduler.core.TheSchedulerServiceImpl] Cannot initialize the scheduler issue! com.atlassian.scheduler.cron.CronSyntaxException: The values for day-of-week must be from 1 to 7. at com.atlassian.scheduler.cron.CronSyntaxException$Builder.build(CronSyntaxException.java:171) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.syntaxErrorAt(CronExpressionParser.java:781) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseNumber(CronExpressionParser.java:842) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseFieldValue(CronExpressionParser.java:848) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSpecialDowNumber(CronExpressionParser.java:508) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSpecialDowField(CronExpressionParser.java:527) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseDowField(CronExpressionParser.java:594) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseQmMonthDow(CronExpressionParser.java:648) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseDomMonthDow(CronExpressionParser.java:661) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseCronExpression(CronExpressionParser.java:673) at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parse(CronExpressionParser.java:164) at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.nextRunTime(RunTimeCalculator.java:97) at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.nextRunTime(RunTimeCalculator.java:70) at com.atlassian.scheduler.caesium.impl.RunTimeCalculator.firstRunTime(RunTimeCalculator.java:47) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleLocalJob(CaesiumSchedulerService.java:163) at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:134) at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJob(DelegatingSchedulerService.java:70) at pl.com.tt.thescheduler.core.TheSchedulerServiceImpl.serviceRegisterJobRunner(TheSchedulerServiceImpl.java:621) at pl.com.tt.thescheduler.core.TheSchedulerServiceImpl.scheduleIssue(TheSchedulerServiceImpl.java:423) at pl.com.tt.thescheduler.core.TheSchedulerServiceImpl.scheduleIssue(TheSchedulerServiceImpl.java:393) at pl.com.tt.thescheduler.core.TheSchedulerServiceImpl.initializeAllJobs(TheSchedulerServiceImpl.java:635) at pl.com.tt.thescheduler.core.TheSchedulerManager.launch(TheSchedulerManager.java:211) at pl.com.tt.thescheduler.core.TheSchedulerManager.onLifecycleEvent(TheSchedulerManager.java:177) at pl.com.tt.thescheduler.core.TheSchedulerManager.onStart(TheSchedulerManager.java:125) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(DefaultLifecycleManager.java:277) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$4.consume(DefaultLifecycleManager.java:274) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecyleAware(DefaultLifecycleManager.java:303) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyOnStartIfStartedAndEnabled(DefaultLifecycleManager.java:273) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.access$300(DefaultLifecycleManager.java:49) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(DefaultLifecycleManager.java:235) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager$3.evaluate(DefaultLifecycleManager.java:232) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyLifecycleAwares(DefaultLifecycleManager.java:258) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.notifyStartableLifecycleAwares(DefaultLifecycleManager.java:231) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.startIfApplicationSetup(DefaultLifecycleManager.java:219) at com.atlassian.sal.core.lifecycle.DefaultLifecycleManager.start(DefaultLifecycleManager.java:210) at com.atlassian.sal.jira.lifecycle.JiraLifecycleManager.onJiraStart(JiraLifecycleManager.java:64) ... 3 filtered at java.lang.reflect.Method.invoke(Method.java:497) at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:48) at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299) at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:107) at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:160) at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:79) at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:73) at com.atlassian.jira.upgrade.PluginUpgradeLauncher.start(PluginUpgradeLauncher.java:30) at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:51) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postTenantArrived$4(DefaultJiraLauncher.java:178) at com.atlassian.jira.startup.DefaultInstantUpgradeManager$StartupTask.run(DefaultInstantUpgradeManager.java:139) at com.atlassian.jira.startup.DefaultInstantUpgradeManager.runTask(DefaultInstantUpgradeManager.java:55) at com.atlassian.jira.startup.DefaultInstantUpgradeManager.doNowOrWhenInstanceBecomesActive(DefaultInstantUpgradeManager.java:42) at com.atlassian.jira.startup.DefaultJiraLauncher.postTenantArrived(DefaultJiraLauncher.java:171) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDBActivated$3(DefaultJiraLauncher.java:159) at com.atlassian.jira.tenancy.DefaultTenantManager.doNowOrWhenTenantArrives(DefaultTenantManager.java:55) at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:156) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:145) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:298) at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:194) at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:135) at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:101) at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31) at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:99) at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:149) at java.lang.Thread.run(Thread.java:745)

Comments (3)

  1. Łukasz Modzelewski
    • changed status to open

    Hi Jóhann,

    Please tell me which version of the plugin you are using, (for jira > 7 there is a 4.3.2 version).

    And secondly could you check if those triggers were validated ?

    best regards,

    Łukasz

  2. Jóhann B. Guðmundsson reporter

    This happened immediately after upgrading from 6.4.14 to 7.0.10 ( we where doing upgrade tests ) which had 3.3.2 during the upgrade and once we had upgraded to jira 7.0.10 we updated all the plugins including this one to 4.3.2. We then proceeded to update jira to 7.0.10 to jira 7.1.10 and then to 7.2.2 and the error is present in all of the 7 instances we tested but no on 6.4.14. I disabled all the scheduled task and the error was still present at startup.

    I went ahead and just deleted all the scheduled task ( roughly 30 of them, I dont have time at dayjob ( interesting to see that if you put @ dayjob in one word it translates to @dayjob in bitbucket ) to validate each and everyone of them and on the production site we have close to 100 or more ) since there was no apparent indicator which trigger was apparently broken in the scheduler nor in jira --> system -- > Scheduler Administration and this atleast this should be fixed since the error went away with that.

    When I have the time I'll try to duplicate this if I can find the triggered that triggered this error.

  3. Log in to comment