Tempo disabled at restart after JIRA upgrade

Customer upgraded Jira and after said upgrade Tempo plugins are disabled upon instance restart.

Newer Jira versions are heavily resource intensive on the instance running the application. By default Jira plugin will be disabled after exceeding 60 seconds default timeout. The workaround would be increasing the plugin timeout to 300 seconds or more, depending on the machine performance.

For more information, please see the link below on how to increase timeout period.
https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html

Instruction for setting properties and options on startup can be found here.
https://confluence.atlassian.com/adminjiraserver070/setting-properties-and-options-on-startup-749383528.html

Additional info on this topic: Some Customers did increase the timeout to 600 and up to 5000 seconds.

This link here should explain that further https://jira.atlassian.com/browse/JRASERVER-60212