Upgrade to greenhopper 5.10.4 can't enable plugin


With Jira 5.0.6 we upgraded to 5.10.4 of the greenhopper plugin. Now the plugin can't be enabled. Seeing the following error message:

/rest/plugins/1.0/com.pyxis.greenhopper.jira-key [plugin.osgi.factory.OsgiPlugin] Detected an error (BundleException) enabling the plugin 'com.pyxis.greenhopper.jira' : Unresolved constraint in bundle com.pyxis.greenhopper.jira [95]: Unable to resolve 95.0: missing requirement [95.0] package; (&(package=org.apache.log4j)(version>=1.2.16)(!(version>=2.0.0))). This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see http://confluence.atlassian.com/x/1xy6D

Any suggestions on how to fix this?



5 answers


Got this one fixed. The problem was we had and older version of log4j in our Jira instance (WAR). Once I upgraded log4j from 1.2.15 to 1.2.16+ (1.2.17 worked for us) the problem went away. I understand the standalone version ships we with the correct library however in the war variation it's in the endorsed lib directory.

Hope that helps!


0 votes

Hi Nathan,

I've logged the bug https://jira.atlassian.com/browse/GHS-5395 regarding this issue, as I've spotted this problem elsewhere as well. It's probably best to downgrade to GreenHopper 5.10.1 for now and wait for that bug to be resolved.




I am affected as well. Luckily I only installed it on our development Environment.



EDIT: I might add the note that this is with JIRA 5.0.3 in my case.


we are affected as well.

But the problem is worse. Jira does not start anymore if you restart your server after this update.

A solution that worked for me, was to replace the existing greenhopper.jar in installed-plugins with an older version (5.10.1), which I downloaded from the marketplace. Now Jira is serving again :).



As a side note, per GHS-5395, this has been fixed and addressed in version


Jeremy Neuharth

Founder | Sycorr

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

618 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you