Unable to Connect to External JIRA Database Due to 'java.sql.SQLException Closed Connection'
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 following exceptions will be found in the logs:
1
2
3
4
5
6
7
8
2008-02-24 08:59:51,034 Finalizer WARN [core.entity.jdbc.SQLProcessor] [SQLProcessor.rollback]: SQL Exception while rolling back insert. Error was:java.sql.SQLException: Closed Connection
2008-02-24 08:59:51,034 Finalizer WARN [NoModule] org.ofbiz.core.entity.jdbc.SQLProcessor
java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:1161)
at org.apache.tomcat.dbcp.dbcp.DelegatingConnection.rollback(DelegatingConnection.java:265)
Cause
When performing an action in JIRA(such as viewing or updating an issue), an error is returned because the database connection has already been closed.
Resolution
In order to prevent this problem from recurring in future:
Shut down JIRA
Add a validation query which JIRA will use when communicating with its database. For more details on how to set the validation query, see:
Restart JIRA
Was this helpful?