JIRA Upgrade Failed and Logs show NullPointerException

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

The upgrade of JIRA failed and unable to access the instance.

The following appears in the atlassian-jira.log:

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:

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

  1. Navigate to the $JIRA_HOME/plugins/installed-plugins folder and remove the Script Runner Plugin.
  2. Restart JIRA.
Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.