JIRA Upgrade Failed and Logs show NullPointerException
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
Symptoms
The upgrade of JIRA failed and unable to access the instance.
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
2013-08-20 16:23:59,483 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] ___ Performing Upgrade ____________________
2013-08-20 16:23:59,804 localhost-startStop-1 INFO [atlassian.jira.upgrade.UpgradeManagerImpl] Performing Upgrade Task: Converting default Custom field values for User and MultiUser types to store the key of the user rather than the username.
2013-08-20 16:23:59,805 localhost-startStop-1 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: java.lang.NullPointerException
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.NullPointerException
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)
at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:112)
at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:87)
at com.atlassian.jira.issue.fields.CustomFieldImpl.getCustomFieldSearcher(CustomFieldImpl.java:1807)
AND:
1
093 Thread-29 WARN [onresolve.jira.groovy.ScriptManagerImpl] Failed to create searcher custom field. Can happen during upgrades.Cause
This is due to the Script Runner Plugin causing the upgrade to fail.
Resolution
Navigate to the
$JIRA_HOME/plugins/installed-pluginsfolder and remove the Script Runner Plugin.Restart JIRA.
Was this helpful?