Jira throws Nullpointer error while accessing Administration > Project page
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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.
*Except Fisheye and Crucible
Problem
Jira throws Nullpointer error while accessing <Jira-URL>/secure/project/BrowseProjects.jspa?s=view_projects.:
The following appears in the atlassian-jira.log
java.lang.NullPointerException
at java.lang.String.compareTo(String.java:1155) [?:1.8.0_171]
at com.atlassian.jira.web.action.browser.ProjectDataForArchivingCollector.collect(ProjectDataForArchivingCollector.java:31) [classes/:?]
at org.apache.lucene.search.Scorer.score(Scorer.java:90) [lucene-core-3.3.0-atlassian-2.jar:3.3.0-atlassian-2 Unversioned directory - 2017-06-30 17:44:27]
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:526) [lucene-core-3.3.0-atlassian-2.jar:3.3.0-atlassian-2 Unversioned directory - 2017-06-30 17:44:27]
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:320) [lucene-core-3.3.0-atlassian-2.jar:3.3.0-atlassian-2 Unversioned directory - 2017-06-30 17:44:27]
at com.atlassian.jira.index.DelegateSearcher.search(DelegateSearcher.java:132) [classes/:?]
at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.search(LuceneSearchProvider.java:300) [classes/:?]
at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.searchOverrideSecurity(LuceneSearchProvider.java:150) [classes/:?]
at com.atlassian.jira.web.action.browser.BrowseProjects.getStatsForArchiving(BrowseProjects.java:200) [classes/:?]
at com.atlassian.jira.web.action.browser.BrowseProjects.access$400(BrowseProjects.java:77) [classes/:?]
at com.atlassian.jira.web.action.browser.BrowseProjects$2.get(BrowseProjects.java:168) [classes/:?]Cause
The problem usually happens after Jira upgrade.
Resolution
To resolve this issue, the administrator will need to run a Jira lock re-index.
Last modified on Nov 23, 2020
Powered by Confluence and Scroll Viewport.