-
Suggestion
-
Resolution: Won't Do
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
In some situation non critical bundled plguin may not be initiated correctly. That will cause the application to lock up and fail to start up.
For e.g. if on upgrade the plugin got disabled due to some errors, on any subsequent startups JIRA reports:
******************************************************************************** JIRA 4.3.4 build: 620 started. You can now access JIRA through your web browser. ******************************************************************************** 2011-06-26 15:26:23,639 main FATAL [atlassian.jira.startup.JiraStartupLogger] *********************************************************************************************************************** The following plugins are required by JIRA, but have not been started: FishEye Plugin (com.atlassian.jirafisheyeplugin) *********************************************************************************************************************** 2011-06-26 15:26:23,661 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked. 2011-06-26 15:26:23,661 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed. 2011-06-26 15:26:24,118 main FATAL [jira.web.dispatcher.JiraWebworkActionDispatcher] ****************************************** JIRA startup failed, JIRA has been locked. ******************************************
The locking mechanism was introduced due to JRA-22633.
The only way to fix this problem is to change the status of the plugin with help of db manipulation.
- is related to
-
- Closed
