Details
-
Bug
-
Resolution: Answered
-
Low
-
3.9.0
-
None
-
Severity 3 - Minor
-
1
-
Description
Summary
FishEye does not restart successfully due to timeout while waiting for plugin to enable.
Increasing the timeout does not resolve the problem.
Expected Results
FishEye restarts successfully and the plugins are loaded.
Actual Results
The below exception is thrown in the atlassian-fisheye-YYYY-MM-DD.log file.
ERROR [main ] com.atlassian.plugin.manager.PluginEnabler PluginEnabler-actualEnable - Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.plugins.atlassian-remote-event-consumer-plugin,com.atlassian.plugins.atlassian-remote-event-common-plugin,com.atlassian.crucible.plugins.fecru-jira-dev-summary-plugin,com.atlassian.plugins.atlassian-remote-event-producer-plugin,com.atlassian.fecru.fecru-analytics-plugin
Note: that the plugin names vary depending on the installed ones.
Environment
This has been reported on FishEye version 3.9.0.
According to the UPM versions, the UPM version should be 2.17 for FishEye 2.7.13 - 3.4.7.
Workaround
The list of available workarounds are available on the Error message after upgrade/restart - Timeout exceeded waiting for service page.
This is the first one to be applied:
- Shutdown FishEye.
- Backup and delete the contents of the following folders:
<FISHEYE_INST>/var/plugins
<FISHEYE_INST>/var/osgi-cache
#Start FishEye (this will recreate the above folders minus any individually downloaded plugins).
Notes
This has been originated from the PLUG-1183 ticket.
Attachments
Issue Links
- relates to
-
PLUG-1183 Loading...