Documentation for JIRA 6.4 (This documentation includes the project navigation sidebar). Not using this? See below:
(JIRA 6.4 without sidebar documentation | JIRA 6.3.x documentation | JIRA Cloud documentation | earlier versions of JIRA)

Title: Surviving Connection Closures  
Author: Nick Menere [Atlassian] May 11, 2005
Last Changed by: Danilo Conrad [Atlassian] Nov 27, 2014
Tiny Link: (useful for email)
Export As: Word  
Incoming Links
Bamboo Knowledge Base (1)
    Page: MySQL Communications link failure
JIRA 6.4.x (11)
    Page: Configuring Datasource for Oracle 10g JDBC drivers
    Page: JIRA 5.1 EAP 2 Release Notes
    Page: JIRA 3.13 Upgrade Guide
    Page: Installing JIRA on Tomcat 6.0 or 7.0
    Page: JIRA 5.1 RC 1 Release Notes
    Page: JIRA 5.1 RC 3 Release Notes
    Page: JIRA 5.1 RC 2 Release Notes
    Page: JIRA 5.1 Beta 1 Release Notes
    Page: JIRA 5.1 EAP 1 Release Notes
    Page: Connecting JIRA to MySQL
    Page: Tuning Database Connections
JIRA Knowledge Base (12)
    Page: Unable to Connect to External JIRA Database Due to 'java.sql.SQLException Closed Connection'
    Page: Troubleshooting Performance Problems
    Page: Closing an Issue Results in 'Column 'ID' cannot be null' Error
    Page: GenericDataSourceException Due to Missing Database Validation Query Configuration
    Page: JIRA Operations Fail with the SQL Exception No more data to read from socket
    Page: Unable to obtain a connection from the underlying connection pool
    Page: Performing Action Results in 'Column ID Cannot be Null'
    Page: Different Issue Status between the View Issue Screen and the Issue Navigator
    Page: 'Invalid State, the Connection Object is Closed' Due to Connection Closure
    Page: MySQL Communication Link Failure
    Page: Upgrade or Export Fails due to GenericDataSourceException Communications Link Failure
    Page: Connection Reset when Accessing the Database
Confluence Knowledge Base (2)
    Page: Handling Oracle Database Connection Pool "Closed Connection" Errors
    Page: Logins Fail Periodically when Delegating User Management to JIRA
JIRA Agile Knowledge Base (3)
    Page: JIRA Agile Operations fail due to Sanity check for setting nextId of issue
    Page: Sub-tasks are not Correctly Associated with Parent Issues in Task Board
    Page: How To Fix "Issue Ranking Operation log entry found where none expected"
Parent Page
    Page: Tuning Database Connections
There are no labels assigned to this page.
Outgoing Links
JIRA 6.4.x (2)     Page: Tuning Database Connections
    Page: JIRA Home Directory