500 page error when using project issue filter
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
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)
診断
環境
- Jira 6.3.15
Diagnostic Steps
- Check if any bundled plugin jar file store at the installed-plugins/plugins folder via JIRA home directory.
原因
There is a jar file overwrite the default bundled plugin version.
ソリューション
Remove the bundled plugin jar file from the installed-plugins/plugins folder via JIRA home directory and restart JIRA to resolved the problem.