Issue searching fails with "NumberFormatException: null" error
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
Summary
Problem
Issue searching is not functioning and it throws the following stack trace instead:
1
2
3
4
5
6
7
java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:454)
at java.lang.Integer.valueOf(Integer.java:582)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.getStableSearchResultsLimit(AbstractIssueTableCreator.java:373)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.collectIssues(AbstractIssueTableCreator.java:156)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.executeNormalSearch(AbstractIssueTableCreator.java:227)
at com.atlassian.jira.plugin.issuenav.service.issuetable.AbstractIssueTableCreator.create(AbstractIssueTableCreator.java:190)
Diagnosis
One of these files has been modified from the default and does not contain the jira.search.stable.max.results parameter:
jira-application.propertiesjpm.xml
Cause
The jira.search.stable.max.results property is not set for the application.
Jira cannot find the Stable Search Limit parameter inside the jpm.xml while performing a search request. Hence throwing the NullPointerException error instead.
Solution
Resolution
A default value is set in jpm.xml for this property and this file should not normally be modified. Instead, add overrides of default properties in the jira-application.properties file as described at Advanced Jira application configuration.
Solution 1
Restore the original content of
jpm.xmlfile by downloading a zip or tarball of the same version you have installed and extracting the file from it.Restart JIRA and perform re-index
Solution 2
Add this property to the jira-application.properties file.
If not already present, create a new file named jira-config.properties under your $JIRA-HOME directory
Copy and paste the following inside jira-config.properties
1jira.search.stable.max.results=1000Restart Jira and perform re-index
Full details are available at Advanced Jira application configuration.
Was this helpful?