Jira's Workflow Integrity checker tool returns a 500 response

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

When using the database integrity checker from Jira to look for Workflow integrity issues, the following response is returned at the User Interface:

(Auto-migrated image: description temporarily unavailable)

Diagnosis

  • The following SQL query returns at least one result:

    1 SELECT id,issuenum,project FROM jiraissue WHERE issuenum IS NULL;

  • The following stack trace can be observed when clicking on Request assistance when the error is shown:

    1 2 3 4 5 com.atlassian.jira.appconsistency.integrity.exception.IntegrityException: Error occurred while performing check. at com.atlassian.jira.appconsistency.integrity.check.WorkflowCurrentStepCheck.doCheck(WorkflowCurrentStepCheck.java:138) [classes/:?] at com.atlassian.jira.appconsistency.integrity.check.WorkflowCurrentStepCheck.preview(WorkflowCurrentStepCheck.java:48) [classes/:?] at com.atlassian.jira.appconsistency.integrity.IntegrityChecker.preview(IntegrityChecker.java:52) [classes/:?] at com.atlassian.jira.appconsistency.integrity.IntegrityChecker.previewWithIds(IntegrityChecker.java:29) [classes/:?]

Cause

  • The integrity checker tool fails to look for Workflow inconsistencies as there are null values at the jiraissue table.

  • There are some changes were done in the database configuration file (e.g. dbconfig.xml) that causes the database connection to close with the following exceptions:

    1 2 3 4 5 6 7 8 9 10 11 12 Caused by: org.ofbiz.core.util.GeneralRuntimeException: Error getting the next result (This ResultSet is closed.) at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:272) [entityengine-1.5.3.jar:?] at com.atlassian.jira.ofbiz.DefaultOfBizListIterator.next(DefaultOfBizListIterator.java:100) [classes/:?] at com.atlassian.jira.ofbiz.WrappingOfBizListIterator.next(WrappingOfBizListIterator.java:68) [classes/:?] at com.atlassian.jira.appconsistency.integrity.check.AbstractEntityRelation.preview(AbstractEntityRelation.java:54) [classes/:?] ... 316 more Caused by: org.postgresql.util.PSQLException: This ResultSet is closed. at org.postgresql.jdbc.PgResultSet.checkClosed(PgResultSet.java:2932) [postgresql-42.2.25.jar:42.2.25] at org.postgresql.jdbc.PgResultSet.next(PgResultSet.java:1951) [postgresql-42.2.25.jar:42.2.25] at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191) [commons-dbcp2-2.1.jar:2.1] at org.apache.commons.dbcp2.DelegatingResultSet.next(DelegatingResultSet.java:191) [commons-dbcp2-2.1.jar:2.1] at org.ofbiz.core.entity.EntityListIterator.next(EntityListIterator.java:266) [entityengine-1.5.3.jar:?]

Solution

Resolution

Option 1. Run "Check Issue Relations" Integrity Check specifically (recommended)

When this behavior is happening, it should be possible to run Check Issue Relations and fix this issue:

  1. Navigate to Administration Menu > System > Troubleshooting & Support > Integrity Checker

  2. Ensure that only the options under 'Check Issue Relations' are selected, and then click on 'check'

  3. Fix all identified errors

  4. Proceed to select all options under 'Check Workflow Integrity', which should work fine after this approach is followed

Option 2. Database update

  1. Remove the NULL entries directly at the database

    1. Stop Jira;

    2. Obtain a database backup in case you need to rollback the changes;

    3. Run the following query:

      1 DELETE FROM jiraissue WHERE issuenum IS NULL;

    4. Start Jira;

  2. Run the integrity checker again to look for workflow integrity issues, which should work fine after the affected entries are deleted at the database.

Option 3. Database Configuration

  1. Check if you have the <pool-remove-abandoned-on-maintenance>true</pool-remove-abandoned-on-maintenance> parameter added in the $JIRA_HOME/dbconfig.xml file.

  2. Remove the entry and restart Jira.

Updated on April 16, 2025
Platform
Data Center only
Product
Jira Software Data Center
On this pageSummaryDiagnosisCauseSolution

Still need help?

The Atlassian Community is here for you.
Ask the Community