I’ve tried to increase the timeout, first 300, then 600. Then, following another thread, I’ve increased the -Xmx to 1024m. At this point I was seeing in the logs that the amount of timed out plugins decreased, I put the timeout to 900, but no improvement came from that.
I doubt it’s a memory problem though, since there’s no OutOfMemoryErrors in the logs. I could increase the timeout by another 300 seconds, but that’s unreasonably long.
Here is the log section on th failed plugins.
___ Plugin System Started _________________
2017-05-16 15:38:36,855 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger]
********************************************************************************************************************************************************************************************************
The following plugins are required by JIRA, but have not been started:
JIRA Projects Plugin(com.atlassian.jira.jira-projects-plugin),
Atlassian Navigation Links Plugin (com.atlassian.plugins.atlassian-nav-links-plugin),
Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin),
Applinks - Plugin - Core (com.atlassian.applinks.applinks-plugin),
Atlassian OAuth Service Provider Plugin (com.atlassian.oauth.serviceprovider),
Embedded Gadgets Plugin (com.atlassian.gadgets.embedded),
Gadget Directory Plugin (com.atlassian.gadgets.directory),
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets),
Atlassian JIRA - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin),
Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin),
Atlassian REST - Module Types (com.atlassian.plugins.rest.atlassian-rest-module),
Atlassian JIRA - Plugins - REST Plugin (com.atlassian.jira.rest),
Opensocial Plugin (com.atlassian.gadgets.opensocial),
Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)
********************************************************************************************************************************************************************************************************
2017-05-16 15:38:36,857 JIRA-Bootstrap ERROR [c.a.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2017-05-16 15:38:36,858 JIRA-Bootstrap INFO [c.a.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed.
2017-05-16 15:38:36,883 JIRA-Bootstrap WARN [c.a.jira.startup.JiraStartupLogger]
and there is the log section on memory use for that sequence
2017-05-16 15:38:36,890 JIRA-Bootstrap INFO [c.a.jira.startup.DefaultInstantUpgradeManager] Late startup launchers took 0s
2017-05-16 15:38:36,911 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 427 MiB. Committed: 567 MiB. Max: 992 MiB
Non-heap memory : Used: 199 MiB. Committed: 213 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 625 MiB. Committed: 780 MiB. Max: 2256 MiB
---------------------------------------------------------------------------------
2017-05-16 15:39:36,445 localhost-startStop-2 INFO [c.a.jira.startup.DefaultJiraLauncher] Stopping launchers
2017-05-16 15:39:36,492 localhost-startStop-2 INFO [c.a.plugin.manager.DefaultPluginManager] Preparing to shut down the plugin system
2017-05-16 15:39:36,508 localhost-startStop-2 INFO [c.a.plugin.manager.DefaultPluginManager] Shutting down the plugin system