Symptoms

There is a large variety of symptoms for this particular case as it can occur at any point a connection to the database is being made. The following is an example of one of the errors that will appear in the atlassian-jira.log:

2012-04-19 17:10:38,896 http-8080-6 ERROR      [500ErrorPage.jsp] Exception caught in 500 page SQL Exception while executing the following:SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM propertyentry WHERE ENTITY_NAME=? AND ENTITY_ID=? AND PROPERTY_KEY=? (I/O Error: Connection reset)
com.opensymphony.module.propertyset.PropertyImplementationException: SQL Exception while executing the following:SELECT ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype FROM jiraschema.propertyentry WHERE ENTITY_NAME=? AND ENTITY_ID=? AND PROPERTY_KEY=? (I/O Error: Connection reset)

Cause

When a database server reboots or a network failure has occurred, all connections in the database connection pool are broken, and JIRA would normally need restarting to recreate those connections. We have some further information on this within our Surviving Connection Closures documentation.

Resolution

1. If you are using HSQL Database, which is supported only for evaluation and not for production environments, switch to a supported database for your JIRA version using with Switching Databases guide.
2. Ensure that the validation query is set as in:
   • Surviving Connection Closures (in the documentation for JIRA 4.4.x and later)
   • Surviving Connection Closures (in the documentation for JIRA 4.3.x and earlier)