Internal Server Error when trying to create/access rapid board

Ryan S September 5, 2013

We recently upgrade our Jira test environment to 6.0.7 with Jira Agile 6.3.0.2. Whenever a user is attempting to create a new rapid board, after clicking create, a generic "Internal Server Error" is given. Looking at the atlassian-greenhopper.log I am presented with multiple instances of this error

2013-09-06 09:12:17,927 http-8080-12 ERROR rsalihar 552x826x1 11pk6ow xxx.xx.x.xx,xxx.xx.x.xx /rest/greenhopper/1.0/rapidview/create/presets [web.rapid.view.RapidViewResource] Unable to complete GreenHopper REST method 
java.lang.ArrayIndexOutOfBoundsException

I cannot figure out what is wrong that is causing this error to be thrown. I have uninstalled and reinstall Jira Agile, re-indexed. Stopped and restarted our server. Just not sure what the issue is right now.

1 answer

0 votes
darylchuah
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 9, 2013

Hi Ryan

I have found a knowledge base article that could possibly address the above issue:

https://confluence.atlassian.com/display/AGILEKB/Internal+Server+Error+while+accessing+Greenhopper+board+due+to+java.lang.NumberFormatException

It could be due to the caches and work directory is not being updated after you perform the upgrade. Can you please try the suggested resolution on the KB article itself.

Hopefully it helps

Ryan S September 18, 2013

Thanks for the suggestion Daryl. Unfortunately this still has not managed to take care of the issue.

I did find this other error farther up in the logs

[plugin.osgi.factory.OsgiPlugin] Detected an error (BundleException) enabling the plugin 'com.pyxis.greenhopper.jira' : Unresolved constraint in bundle com.pyxis.greenhopper.jira [119]: Unable to resolve 119.0: missing requirement [119.0] package; (package=com.atlassian.core.action).  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 https://developer.atlassian.com/x/mQAN

I went to the link that is given, but don't fuly understand what to do, or what to point my Web Admin to do as I don't directly administer all parts of our Jira distribution.

LASER March 11, 2014

Was there any resolution to this problem?

Suggest an answer

Log in or Sign up to answer