Upgrade from 6.2.3 to 7.0.11 Results in JIRA Startup Failed - Plugins Not Started

[SmartTechPD]

I'm trying to upgrade to the latest version of JIRA and after upgrading to 7.0.11 I can't get my JIRA to start.  I'm on a Windows Server 2008 R2 connected to a MySQL DB.

I've:

1. Cleared plugin cache (every attempt to start).
2. Removed my lock file (every attempt to start).
3. Confirmed Java/MySQL version compatibility.
4. Modified the setenv.bat to:
   1. set JVM_SUPPORT_RECOMMENDED_ARGS= -Datlassian.plugins.enable.wait=700
   2. set JVM_MAXIMUM_MEMORY=850m

Yet nothing works.  Any help is greatly appreciated - I'm not sure what else to do.

Here is my error as of now:

The following plugins are required by JIRA, but have not been started:

• Gadget Directory Plugin (com.atlassian.gadgets.directory)
• Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
• Atlassian JIRA - Plugins - Issue Search (com.atlassian.jira.jira-issue-nav-plugin)
• Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)
• Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest)

I also see an issue in the log about a timer:

018-03-27 18:57:52,340 Spring DM Context Creation Timer ERROR      [c.a.p.osgi.factory.OsgiPlugin] Unable to start the plugin container for plugin 'com.atlassian.applinks.applinks-cors-plugin'
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.applinks-cors-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)(objectClass=com.atlassian.sal.api.net.RequestFactory))
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)
2018-03-27 18:57:52,356 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.internal.support.ExtenderConfiguration] Application context refresh failed (NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.applinks.applinks-cors-plugin, config=osgibundle:/META-INF/spring/*.xml))
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.applinks-cors-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)(objectClass=com.atlassian.sal.api.net.RequestFactory))
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)
2018-03-27 18:57:52,356 Spring DM Context Creation Timer ERROR      [o.e.g.b.e.i.dependencies.startup.DependencyWaiterApplicationContextExecutor] Unable to create application context for [com.atlassian.applinks.applinks-cors-plugin], unsatisfied dependencies: Dependency on [(objectClass=com.atlassian.sal.api.net.RequestFactory)] (from bean [&requestFactory]), Dependency on [(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)] (from bean [&authenticationConfigurationManager]), Dependency on [(objectClass=com.atlassian.applinks.api.ApplicationLinkService)] (from bean [&applicationLinkService]), Dependency on [(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)] (from bean [&typeAccessor])
org.springframework.context.ApplicationContextException: Application context initialization for 'com.atlassian.applinks.applinks-cors-plugin' has timed out waiting for (|(objectClass=com.atlassian.applinks.spi.auth.AuthenticationConfigurationManager)(objectClass=com.atlassian.applinks.api.ApplicationLinkService)(objectClass=com.atlassian.applinks.core.InternalTypeAccessor)(objectClass=com.atlassian.sal.api.net.RequestFactory))
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.timeout(DependencyWaiterApplicationContextExecutor.java:489)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.access$000(DependencyWaiterApplicationContextExecutor.java:54)
    at org.eclipse.gemini.blueprint.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$WatchDogTask.run(DependencyWaiterApplicationContextExecutor.java:109)
    at java.util.TimerThread.mainLoop(Timer.java:555)
    at java.util.TimerThread.run(Timer.java:505)

[SmartTechPD · Accepted solution]

I ended up being able to resolve this myself.  Please see what I've done above and then:

Ensure all your plugins are enabled even if you arn't using them (for instance HipChat).  Plugins are bundled differently now and critical plugins maybe in bundles you previously had disabled.

SELECT * FROM pluginstate where pluginenabled = 'false';

UPDATE pluginstate SET pluginenabled='true' WHERE pluginkey='<pluginkey from query above>';