Invalid state errors when editing/viewing issues in Jira server
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 JIRA application fails to save or display edited issues, and the following error is logged in logs:
1
2
3
com.opensymphony.module.propertyset.PropertyImplementationException: SQL Exception while executing the following:
SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM Jira_schema.propertyentry WHERE ENTITY_NAME=? AND ENTITY_ID=? AND PROPERTY_KEY, propertytype FROM Jira_schema.propertyentry
WHERE ENTITY_NAME=? AND ENTITY_ID=? AND PROPERTY_KEY=? (Invalid state, the Connection object is closed.)
Cause
The problem is caused due to database connections being closed. Generally, this happens when:
The server times out the connections due to inactivity
OR
The database server is restarted.
Corrupted database tables can cause this as well.
Resolution
Enable connection checking by adding a validation query which the JIRA application will use when communicating with its database. For more details on how to set the validation query, see:
Was this helpful?