404 Error message on GreenHopper: Error creating bean with name com.pyxis.greenhopper.jira.actions.LicenseAction
Symptoms
When trying to access GreenHopper administration pages or trying to see license details, you might face a 404 error and the following appears in the atlassian-jira.log
:
http-8080-6 ERROR testuser 1014x263x1 59nipb 192.168.5.1 /secure/GHLicense.jspa [jira.config.webwork.JiraActionFactory] Error autowiring Action 'com.pyxis.greenhopper.jira.actions.LicenseAction'.
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'com.pyxis.greenhopper.jira.actions.LicenseAction': Unsatisfied dependency expressed through constructor argument with index 0 of type [com.pyxis.greenhopper.GreenHopper]: : No unique bean of type [com.pyxis.greenhopper.GreenHopper] is defined: Unsatisfied dependency of type [interface com.pyxis.greenhopper.GreenHopper]: expected at least 1 matching bean; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.pyxis.greenhopper.GreenHopper] is defined: Unsatisfied dependency of type [interface com.pyxis.greenhopper.GreenHopper]: expected at least 1 matching bean
at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:591)
at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:193)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440)
Cause
This error is caused by an incompatibility between GreenHopper and other third-party plugins.
Resolution
Disable all third-party plugins (except GreenHopper).
Restart your JIRA instance.
Try to access GreenHopper administration again.
You may consider re-enabling the third-party plugins one by one, to identify the culprit of this incompatibility.