Trying to view a Project in Jira throws java.lang.NumberFormatException: null
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
When trying to get in one of the projects in the project list, it fails with the following stack trace:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Unknown Source)
at java.lang.Long.valueOf(Unknown Source)
at com.atlassian.jira.plugin.issuenav.service.issuetable.IssueDocumentAndIdCollector.addMatch(IssueDocumentAndIdCollector.java:208)
at com.atlassian.jira.plugin.issuenav.service.issuetable.IssueDocumentAndIdCollector.computeResult(IssueDocumentAndIdCollector.java:186)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.executeNormalSearch(AbstractIssueTableCreator.java:236)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.create(AbstractIssueTableCreator.java:198)
at com.atlassian.jira.plugin.issuenav.service.issuetable.DefaultIssueTableService.createIssueTableFromCreator(DefaultIssueTableService.java:165)
at com.atlassian.jira.plugin.issuenav.service.issuetable.DefaultIssueTableService.getIssueTable(DefaultIssueTableService.java:279)
at com.atlassian.jira.plugin.issuenav.service.issuetable.DefaultIssueTableService.getIssueTableFromFilterWithJql(DefaultIssueTableService.java:130)
at com.atlassian.jira.plugin.issuenav.IssueNavAction.performSearch(IssueNavAction.java:1161)
at com.atlassian.jira.plugin.issuenav.IssueNavAction.doNav(IssueNavAction.java:360)
at com.atlassian.jira.plugin.issuenav.IssueNavAction.doDefault(IssueNavAction.java:244)
at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70)
at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
Cause
This happens because Jira expects a number value when loading the page, but no value is returned from the indexes. This is most likely to happen if the search indexes are corrupted.
For example, this may happen if Jira hit the limit of open files allowed, as described on Too many open files error in Jira server.
Resolution
Trigger a full re-index in Jira:
If this problem was caused by the Too Many Open Files error, please follow Too many open files error in Jira server before proceeding.
Browse to Administration > System > Indexing,
Trigger Lock Jira and Rebuild the index to fully reindex Jira
During the reindex operation JIRA cannot be accessed. Depending on the size of the instance this operation may take a while, so if needed please run this off business hours.
Was this helpful?