[JCR-934] Failed to reconnect to database after network connection was dropped

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 1.3
• Assignee: Unassigned
• Reporter: Xiaohua Lu
• Created: 21/May/07 15:12
• Updated: 08/Aug/07 06:58
• Resolved: 23/May/07 14:59

Description

I have read similar bug report before and thought the connection to database will be retried after a dropped network connection. But in my cluster environment, both the bundled persistent manager and database journal failed to reconnect to database after the network is restored and I have to restart all instances in order to regain db connection. The exceptions are :

11:05:38,994 ERROR BundleDbPersistenceManager:894 - [http-8180-Processor25] fail
ed to read bundle: 08b8bb71-4671-4cc2-bee5-14b4522f678a: java.sql.SQLException:
Invalid state, the Connection object is closed.

11:07:16,914 ERROR ClusterNode:257 - [ClusterNode-mcrperf1] Periodic sync of journal failed: Unable to return record iterater.

I am using

net.sourceforge.jtds.jdbc.Driver for a mssql server 2005.

Issue Links

• is related to: JCR-940 add db connection autoConnect for BundleDbPersistenceManager.
• is related to: JCR-927 DatabaseJournal needs connection reestablishment logic