Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-6402

FishEye does not successfully restart due to timeout while waiting for plugin to enable

      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:

      1. Shutdown FishEye.
      2. 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.

            [FE-6402] FishEye does not successfully restart due to timeout while waiting for plugin to enable

            Atlassian Update – 10 January 2022

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

            We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details.

            If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 10 January 2022 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details. If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates. Kind regards Marek Parfianowicz Development Team Lead

              Unassigned Unassigned
              ccurti Caterina Curti
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: