Atlassian JIRA | Justin Burke | 2 years ago
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    h3. Description: When using the Background Reindex or Index Recovery functionality, users will encounter a 500 error page which will display a stack trace similar to the following: {code}Referer URL: http://jira-dev/secure/admin/jira/IndexProgress.jspa?taskId=15203 java.lang.NullPointerException java.lang.NullPointerException at com.atlassian.jira.web.action.admin.index.IndexAdminImpl.doProgress( at sun.reflect.GeneratedMethodAccessor1683.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke( at webwork.util.InjectionUtils.invoke( at webwork.action.ActionSupport.invokeCommand( at webwork.action.ActionSupport.execute( at com.atlassian.jira.action.JiraActionSupport.execute( at webwork.interceptor.DefaultInterceptorChain.proceed( at webwork.interceptor.NestedInterceptorChain.proceed( at webwork.interceptor.ChainedInterceptor.intercept( at webwork.interceptor.DefaultInterceptorChain.proceed( at webwork.dispatcher.GenericDispatcher.executeAction( at webwork.dispatcher.GenericDispatcher.executeAction( at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service( at javax.servlet.http.HttpServlet.service({code} It seems like the actual indexing process (Background Reindex or Index Recovery) completes in the logs: h4. Example from Background Reindex {code}2015-06-19 09:11:38,563 ISSUE-indexQueue:thread-1 INFO SPNG3 763x115x1 1g85w3l /secure/admin/IndexReIndex.jspa [action.admin.index.IndexAdminImpl] Re-indexing is 97% complete. Current index: Issue 2015-06-19 09:11:43,912 JiraTaskExectionThread-4 INFO SPNG3 533x85327x2 bn3lrn /secure/admin/IndexReIndex.jspa [jira.issue.index.DefaultIndexManager] 79795 issues reindexed in the background, in 1078825 millis. 2015-06-19 09:11:43,929 JiraTaskExectionThread-4 ERROR SPNG3 533x85327x2 bn3lrn /secure/admin/IndexReIndex.jspa [jira.util.index.CompositeIndexLifecycleManager] Reindex All In Background FAILED. Indexer: DefaultIndexManager: paths: [/data/jira/caches/indexes/comments, /data/jira/caches/indexes/issues, /data/jira/caches/indexes/changes, /data/jira/caches/indexes/worklogs] java.lang.NullPointerException at com.atlassian.jira.issue.index.DefaultIssueIndexer$3.consume( 2015-06-19 09:11:43,931 JiraTaskExectionThread-4 INFO SPNG3 533x85327x2 bn3lrn /secure/admin/IndexReIndex.jspa [action.admin.index.IndexAdminImpl] Re-indexing finished{code} h4. Example from Index Recovery {code}2015-07-01 07:46:54,003 JiraTaskExectionThread-1 INFO spjsf 466x624023x1 17ake2e /secure/admin/jira/IndexRecover.jspa [action.admin.index.IndexAdminImpl] Re-indexing started 2015-07-01 07:46:58,918 JiraTaskExectionThread-1 INFO spjsf 466x624023x1 17ake2e /secure/admin/jira/IndexRecover.jspa [jira.index.ha.DefaultIndexRecoveryManager] Recovering search indexes - 1% complete... 2015-07-01 07:47:05,305 JiraTaskExectionThread-1 INFO spjsf 466x624023x1 17ake2e /secure/admin/jira/IndexRecover.jspa [jira.index.ha.DefaultIndexRecoveryManager] Recovering search indexes - 20% complete... 2015-07-01 07:47:05,341 JiraTaskExectionThread-1 INFO spjsf 466x624023x1 17ake2e /secure/admin/jira/IndexRecover.jspa [action.admin.index.IndexAdminImpl] Index Recovery finished{code} h3. Steps to Reproduce (i)I have not been able to reproduce this locally with Background Reindexing, but I HAVE been able to reproduce locally using the Index Recovery functionality. These steps refer to that process # Set up Index Recovery # Allow for the Index Recovery process to run at the appointed time (for testing, you can set the time for 5 or 10 minutes in the future) # Once an index recovery backup zip is created, enter in the appropriate zip file name into the UI and click *Recover*. # Near the end of the recovery process, note the 500 error page. h4. Workaround Since the actual indexing process seems to work fine, a workaround may not be needed. However, users can run a full, locking index in lieu of either process to rebuild their indexes from the database if their situations warrant it.

    Atlassian JIRA | 2 years ago | Justin Burke

    Root Cause Analysis

    1. java.lang.NullPointerException

      No message provided

      at com.atlassian.jira.issue.index.DefaultIssueIndexer$3.consume()
    2. com.atlassian.jira
      1. com.atlassian.jira.issue.index.DefaultIssueIndexer$3.consume(
      1 frame