Jira restarts after Plugin update

[ChristopherChilds]

Hello,

We are seeing an issue where Jira restarts after some plugins are updated. This does not happen all the time only some plugins. I am not sure if this is dependant on the size of the plugin. The last plugin this happened with was Atlassian Universal Plugin Manager.

I am not 100% sure what to look for in the logs. However, we can see that shortly after the plugin update has been initiated that all plugins are then stopped and the server, I assume, is restarted and not crashed.

[Radek Dostál · Accepted solution]

Plugins don't restart the Jira process. However UPM is expected to, because it manages all plugins: https://confluence.atlassian.com/upm/updating-the-universal-plugin-manager-273875702.html

[ChristopherChilds]

Strange,
According to the documentation when you update from the Manage Apps (online) then you do not restart;

Click Update now automatically download and apply the update.
You don't need to restart the application after the update. For certain version updates, you'll need to refresh the browser page, as indicated by an onscreen message.

[ChristopherChilds]

Ok,

I see what happens. It restarts all the plugins:
https://jira.atlassian.com/browse/JRASERVER-69963

Upgrading UPM triggers all apps/applications to restart because of the licensing API provided by UPM. This can cause Jira to return 404 and other errors while the UPM upgrade is in progress, effectively causing downtime.

[Matthew Martin]

I want to add my voice to this.

We are seeing a growing number of inter-dependencies between addons. A great example of one such interdependency is the Atlassian-made cloud migration addon.

If you disable or update this addon, it will trigger a cascading restart of other add-ons making the impacts to a JIRA environment far more significant than what you were doing.

This is becoming a severe issue for us in our data centre environment as JIRA has no mechanism to expose these interdependencies or alert a user to what will happen if you change an addon that is a dependency of another addon. 

The only way to mitigate this risk is to carefully watch what happens in your non-prod environment when you update the addon and identify if other addons are affected.

These are the addons I currently know that will likely trigger wide-reaching restarts in your environments:

• Automation for JIRA Validated as not impacted
• Scriptrunner for JIRA Validated as not impacted
• Configuration Manager by Botron
• Cloud Migration addon

Dec 13/2022 Edit: We've discussed this with Atlassian and performed internal testing. The issue is Configuration Manager. After removing the addon from our environment, Automation for JIRA and Scriptrunner can independently be restarted.

[ChristopherChilds]

Relating to the dependencies, we have seen one regarding Jira Automation and third party tools. In your list we are familiar with Automation and Scriptrunner.

If we were to disable Scriptrunner and then disable Automation and re-enable Script Runner and then re-enable Automation, then all the automation rules will fail. Regardless of using the third party components.:
https://confluence.atlassian.com/automationkb/automation-for-jira-all-rules-are-failing-to-be-executed-due-to-the-error-service-proxy-has-been-destroyed-1167747337.html