-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: None
-
None
New Studio hosts have a GreenHopper link, but clicking on it results in a stacktrace:
HTTP Status 404 - Could not execute action [GreenHopper]:Action 'GreenHopper' not found or could not be initialized: Class not found<p><small><small><pre>java.lang.IllegalArgumentException: Action 'GreenHopper' not found or could not be initialized: Class not found at com.atlassian.jira.config.webwork.JiraActionFactory$JiraPluginActionFactory.getActionImpl(JiraActionFactory.java:295) at webwork.action.factory.ScriptActionFactoryProxy.getActionImpl(ScriptActionFactoryProxy.java:54) at webwork.action.factory.XMLActionFactoryProxy.getActionImpl(XMLActionFactoryProxy.java:54) at webwork.action.factory.PrefixActionFactoryProxy.getActionImpl(PrefixActionFactoryProxy.java:102) at
When a new Studio host comes up, the last upgrade task to run is:
2009-06-01 12:10:59.103999500 2009-06-01 12:10:59,103 TP-Processor2 INFO [sal.jira.upgrade.JiraPluginUpgrader] Plugin com.atlassian.studio.theme.jira upgrade completed. Current version is: 42
However just like when enabling the plugin through the web interface, JIRA requires a restart before the plugin will work.
- relates to
-
CLOUD-1366 Greenhopper plugin requires restart to activate
-
- Closed
-