Internal server error when opening Sprint Report

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

Users are unable to access the Sprint reports on Rapid Board and the following appear in the log files:

1 2 3 4 5 6 7 8 9 10 11 12 com.sun.jersey.server.impl.application.WebApplicationImpl onException SEVERE: Internal server error java.lang.NullPointerException at com.atlassian.greenhopper.web.rapid.sprint.SprintsResource$1.call(SprintsResource.java:75) at com.atlassian.greenhopper.web.rapid.sprint.SprintsResource$1.call(SprintsResource.java:56) at com.atlassian.greenhopper.web.util.RestCall.response(RestCall.java:48) at com.atlassian.greenhopper.web.AbstractResource.response(AbstractResource.java:48) at com.atlassian.greenhopper.web.rapid.sprint.SprintsResource.getAllSprintsForRapidView(SprintsResource.java:55) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597)

Cause

This error is caused by invalid or corrupted indexes on JIRA. It is necessary to re-build them to fix this problem.

Resolution

  1. Shutdown your JIRA instance.

  2. Delete the content of the following folder:

    ℹ️ This is a temporary directory and will be recreated upon JIRA restart.

    1 $JIRA_HOME/caches/indexes
  3. Restart your JIRA instance.

  4. Run the Re-index (Administration -> System -> Indexing). Please note that your instance will be unavailable while the re-index runs.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.