500 page error when using project issue filter
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the server and data center platforms.
Problem
After click on the Project issue filter (such as Assign to Me link), JIRA will throw 500 error page. It will happen if user click on the "Issues > Search for issues" menu as well.
The following will appears in the web browser:
Referer URL: <base-url>/browse/<project>/?selectedTab=com.atlassian.jira.jira-projects-plugin:issues-panel
java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
java.lang.NoClassDefFoundError: org/apache/commons/lang3/StringUtils
at com.atlassian.jira.components.query.DefaultSearcherService.getEditHtml(DefaultSearcherService.java:474)
at com.atlassian.jira.components.query.DefaultSearcherService.getValueResults(DefaultSearcherService.java:259)
at com.atlassian.jira.components.query.DefaultSearcherService.getSearchResults(DefaultSearcherService.java:180)
at com.atlassian.jira.components.query.DefaultSearcherService.searchWithJql(DefaultSearcherService.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
Diagnosis
Environment
- JIRA 6.3.15
Diagnostic Steps
- Check if any bundled plugin jar file store at the installed-plugins/plugins folder via JIRA home directory.
Cause
There is a jar file overwrite the default bundled plugin version.
Resolution
Remove the bundled plugin jar file from the installed-plugins/plugins folder via JIRA home directory and restart JIRA to resolved the problem.
Last modified on Mar 30, 2016
Powered by Confluence and Scroll Viewport.