1. TT APDC Avatar TT APDC
  2. Atlassian Plugin Development Center
  3. The Scheduler
  4. Issues

After upgrade to 7.0.11

Issue #266 resolved
FlexDanmark Atlassian-Licenses created an issue

... and also further to 7.5.2, when starting Jira;

JIRA-Bootstrap FATAL      [p.c.t.thescheduler.service.TheSchedulerServiceImpl] Cannot initialize the scheduler issue!
com.atlassian.scheduler.cron.CronSyntaxException: The step interval character '/' must be followed by a positive integer.
        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.parseStep(CronExpressionParser.java:854)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSlashInterval(CronExpressionParser.java:244)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseNameExpression(CronExpressionParser.java:309)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSimpleExpression(CronExpressionParser.java:324)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSimpleField(CronExpressionParser.java:344)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseSimpleFieldToRule(CronExpressionParser.java:361)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseMonthField(CronExpressionParser.java:587)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseDomMonthQm(CronExpressionParser.java:654)
        at com.atlassian.scheduler.caesium.cron.parser.CronExpressionParser.parseDomMonthDow(CronExpressionParser.java:663)
        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.scheduleClusteredJob(CaesiumSchedulerService.java:179)
        at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.scheduleJob(CaesiumSchedulerService.java:137)
        at com.atlassian.scheduler.core.DelegatingSchedulerService.scheduleJob(DelegatingSchedulerService.java:70)
        ... 2 filtered
        at java.lang.reflect.Method.invoke(Method.java:498)
        at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
        at com.sun.proxy.$Proxy52.scheduleJob(Unknown Source)
        ... 2 filtered
        at java.lang.reflect.Method.invoke(Method.java:498)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:302)
        at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.doInvoke(ServiceInvoker.java:56)
        at org.eclipse.gemini.blueprint.service.importer.support.internal.aop.ServiceInvoker.invoke(ServiceInvoker.java:60)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invokeUnprivileged(ServiceTCCLInterceptor.java:70)
        at org.eclipse.gemini.blueprint.service.util.internal.aop.ServiceTCCLInterceptor.invoke(ServiceTCCLInterceptor.java:53)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.eclipse.gemini.blueprint.service.importer.support.LocalBundleContextAdvice.invoke(LocalBundleContextAdvice.java:57)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:133)
        at org.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:121)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:208)
        at com.sun.proxy.$Proxy2531.scheduleJob(Unknown Source)
        at pl.com.tt.thescheduler.service.TheSchedulerServiceImpl.serviceRegisterJobRunner(TheSchedulerServiceImpl.java:263)
        at pl.com.tt.thescheduler.service.TheSchedulerServiceImpl.scheduleJob(TheSchedulerServiceImpl.java:210)
        at pl.com.tt.thescheduler.service.TheSchedulerServiceImpl.scheduleJob(TheSchedulerServiceImpl.java:179)
        at pl.com.tt.thescheduler.service.TheSchedulerServiceImpl.initializeAllJobs(TheSchedulerServiceImpl.java:278)
        at pl.com.tt.thescheduler.core.TheSchedulerManager.launch(TheSchedulerManager.java:233)
        at pl.com.tt.thescheduler.core.TheSchedulerManager.onLifecycleEvent(TheSchedulerManager.java:199)
        at pl.com.tt.thescheduler.core.TheSchedulerManager.onStart(TheSchedulerManager.java:147)
        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:498)
        at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:40)
        at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1$1.run(AsynchronousAbleEventDispatcher.java:38)
        at com.google.common.util.concurrent.MoreExecutors$DirectExecutorService.execute(MoreExecutors.java:299)
        at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:88)
        at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:204)
        at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:115)
        at com.atlassian.plugin.event.impl.DefaultPluginEventManager.broadcast(DefaultPluginEventManager.java:83)
        at com.atlassian.jira.upgrade.PluginUpgradeLauncher.start(PluginUpgradeLauncher.java:29)
        at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:52)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:181)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:155)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:304)
        at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:199)
        at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:146)
        at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:105)
        at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
        at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:103)
        at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:157)
        at java.lang.Thread.run(Thread.java:745)

Also, it appears that many of my scheduled tasks are cloned three, four and five times?

This is in a test environment with a clone of the production server, so everything is good, however I cannot upgrade because of this.

Any suggestions?

Regards, Martin

Comments (22)

  1. Łukasz Modzelewski
    • changed status to open

    Hi Martin,

    Basically we need to know everything about your Jira instance from which you've upgraded to 7.0.11 and details about that cron expression.

    • what was the previous version
    • if it was a datacenter (number of nodes)
    • database type and version
    • version of The Scheduler (before / after upgrade)
    • screen of the manage scheduled issues table with all cron expression visible
    • screen from system tab Scheduler Administration from The Scheduler Plugin (maybe some jobs are invalid, link; /secure/admin/SchedulerAdmin.jspa "
    • atlassian-jira.log file - for further investigation

    You can attach it here or send it directly at support.atlassian@tt.com.pl

    Cheers,

    Łukasz

  3. FlexDanmark Atlassian-Licenses reporter

    Hi Łukasz,

    I'll make a clean upgrade again (as other things was attempted in the previous run) and I'll get back to you with the mentioned details if the problem persist.

    Have a nice day, Martin

  4. FlexDanmark Atlassian-Licenses reporter

    Łukasz, backstory: I inherited a Jira instance, which I'm attempting to upgrade. I'ts a single on-premise server instance, Jira 6.4.8 running on MySQL 5.6.33, TheScheduler 3.3.6.

    Can I expect a clean upgrade run of The Scheduler to 5.0.10, or do I have to land on specific versions in order to upgrade?

  5. Łukasz Modzelewski

    Yes, upgrade to latest version should be smooth and painless.

    So please try again, and let us know.

  6. FlexDanmark Atlassian-Licenses reporter

    I have sent a few screenshots to you.

    Procedure from Jira 6.4.8; stop instance, remove plugins from installed-plugins and plugin-cache (in order to be able to upgrade, as we have a lot of plugins) and as pr Atlassian recommendation. Upgrade to 7.0.11 to upgrade Jira database, Upgrade to 7.5.2. Install TheScheduler again.

    Immediately after install of plugin, going to the Manage Schedules yields the same result; every Schedule is found 6 times. Same entries in log as this issue begins with.

  8. Łukasz Modzelewski

    We have successfully reproduced this, now we are looking for the root cause of the problem.

    Thank you for reporting this.

    I'll keep you updated :)

  10. Dominik M.

    Dear User,

    I've tried my best and was able to reproduce the error (duplicated Scheduled Issue entries) only once out of more than 15 attempts (also with different variants of performing mentioned by you steps). The biggest puzzle right now is that there is nothing of particular interest present in atlassian-jira.log file, so at the moment I need to gather more information.

    I've attached theschedulerpro-5.0.10_migration_logging.jar file - if possible please install it in a test environment (please do so after upgrade to JIRA 7.5.2) and please check if duplcates are present and provide us with atlassian-jira.log file.

    Many thanks, Dominik

  12. Łukasz Modzelewski

    Please let us know if it worked.

    if not please send us atlassian-jira.log file at support.atlassian@tt.com.pl

    Cheers,

    Łukasz

  14. FlexDanmark Atlassian-Licenses reporter

    Hello Łukasz,

    Happy newyear to you!

    I've been otherwise occupied, sorry for that. End of your changed priorities here.

    I've upgraded to a Jira 7.6.2 - can I use your plugin and expect the same behavior to be seen there, or should you build it for me to Jira 7.6.2 ?

    Br, Martin

  15. Dominik M.

    Dear Martin,

    The attached add-on in in compliance with Jira 7.6.2 - please check it in test environment to see if duplcates are present and provide us with atlassian-jira.log file.

    Regards, Dominik

  17. Łukasz Modzelewski

    Hi Martin,

    It is getting a bit messy here.

    The best would be if we start all over, and you try with the latest version of The Scheduler - from the Marketplace (5.1.1), and Jira 7.6.2 - to make sure it will work now (there is no turning back ;) )

    So, please try this and let us know about the results, and if anything goes wrong send us "atlassian-jira.log file" at support.atlassian@tt.com.pl

    Cheers,

    Łukasz

  20. FlexDanmark Atlassian-Licenses reporter

    I just upgraded using your supplied .jar file.

    Much to my dissapointment - it didn't multiply the tasks - which, for me, is a first. :-/ ?

    I have changed exactly one thing; the database is now a PostGreSQL 9.5 - (export, xml-cleanr, import) which has fixed heaps of other annoyances for us.

    I'll synchronize from production (which is upgraded, ex TheScheduler) - and try again. If it does not multiply, then I will not pursue this any further, and I'll attribute it to MySQL<-> Jira issues.

    I'll get back.

    Best, Martin

  23. Log in to comment
Assignee
Type
bug
Priority
critical
Status
resolved
Version
Scheduler 5.x
Votes
0
Watchers
1