Startup after Jira 7 upgrade failed

I've upgraded our MS SQl based JIRA 6.4.5 Instance to JIRA Software 7.0.3. 
First it looks okay. getting this message:

JIRA 7.0.3 build: 70112 started. You can now access JIRA through your web browser.

But suddenly after I get this error message. Can't start JIRA: 

Anybody an idea what the problem can be? 

2015-12-10 14:07:38,574 localhost-startStop-1 ERROR [c.a.jira.scheduler.JiraSchedulerLauncher] A RuntimeException occurred during JiraSchedulerLauncher servlet context initialisation - deadline cannot be negative.
java.lang.IllegalArgumentException: deadline cannot be negative
at com.atlassian.util.concurrent.Assertions.isTrue(Assertions.java:32)
at com.atlassian.scheduler.caesium.impl.QueuedJob.<init>(QueuedJob.java:35)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.addOrReplaceJob(SchedulerQueueImpl.java:113)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobsFromDao(SchedulerQueueImpl.java:171)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobsUnderLock(SchedulerQueueImpl.java:153)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobs(SchedulerQueueImpl.java:136)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.refreshClusteredJobs(CaesiumSchedulerService.java:356)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.startImpl(CaesiumSchedulerService.java:266)
at com.atlassian.jira.scheduler.JiraCaesiumSchedulerService.startImpl(JiraCaesiumSchedulerService.java:40)
at com.atlassian.scheduler.core.AbstractSchedulerService.start(AbstractSchedulerService.java:206)
at com.atlassian.jira.scheduler.JiraSchedulerLauncher.proceedIfAllClear(JiraSchedulerLauncher.java:41)
at com.atlassian.jira.scheduler.JiraSchedulerLauncher.start(JiraSchedulerLauncher.java:27)
at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:55)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$475(DefaultJiraLauncher.java:133)
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:120)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$473(DefaultJiraLauncher.java:89)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:87)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:79)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2015-12-10 14:07:38,585 localhost-startStop-1 ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalArgumentException: deadline cannot be negative
at com.atlassian.util.concurrent.Assertions.isTrue(Assertions.java:32)
at com.atlassian.scheduler.caesium.impl.QueuedJob.<init>(QueuedJob.java:35)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.addOrReplaceJob(SchedulerQueueImpl.java:113)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobsFromDao(SchedulerQueueImpl.java:171)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobsUnderLock(SchedulerQueueImpl.java:153)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueImpl.refreshClusteredJobs(SchedulerQueueImpl.java:136)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.refreshClusteredJobs(CaesiumSchedulerService.java:356)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.startImpl(CaesiumSchedulerService.java:266)
at com.atlassian.jira.scheduler.JiraCaesiumSchedulerService.startImpl(JiraCaesiumSchedulerService.java:40)
at com.atlassian.scheduler.core.AbstractSchedulerService.start(AbstractSchedulerService.java:206)
at com.atlassian.jira.scheduler.JiraSchedulerLauncher.proceedIfAllClear(JiraSchedulerLauncher.java:41)
at com.atlassian.jira.scheduler.JiraSchedulerLauncher.start(JiraSchedulerLauncher.java:27)
at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:55)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$475(DefaultJiraLauncher.java:133)
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:120)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$473(DefaultJiraLauncher.java:89)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:87)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:79)
... 5 filtered
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

1 answer

1 accepted

0 votes
Accepted answer

I've found the solution for my problem. In my case the JIRA Service Desk Plugin was the reason for this upgrade failure. To solve my problem I've done these steps:

  • downgrade to JIRA 6.4.5 again (db & plugin/cache restore)
  • started JIRA 6.4.5 again, uninstalled the service desk plugin  
  • stop JIRA
  • deploy new JIRA 7
  • start JIRA 7
  • refresh all add-ons with the latest version

When upgrading best solution is to disable/uninstall all user-installed addons before doing the upgrade!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,484 views 15 20
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you