You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Xiaohua Lu (JIRA)" <ji...@apache.org> on 2007/05/21 17:13:16 UTC
[jira] Created: (JCR-934) Failed to reconnect to database after
network connection was dropped
Failed to reconnect to database after network connection was dropped
--------------------------------------------------------------------
Key: JCR-934
URL: https://issues.apache.org/jira/browse/JCR-934
Project: Jackrabbit
Issue Type: Bug
Affects Versions: 1.3
Reporter: Xiaohua Lu
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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-934) Failed to reconnect to database after
network connection was dropped
Posted by "Stefan Guggisberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg resolved JCR-934.
-----------------------------------
Resolution: Invalid
the 'auto reconnect' feature is currently only implemented in
DatabasePersistenceManager & DatabaseFileSystem (see JCR-645).
there's an improvement issue (JCR-927) wrt supporting this feature
in DatabaseJournal.
feel free to post a similar improvement issue for BundleDbPersistenceManager.
> Failed to reconnect to database after network connection was dropped
> --------------------------------------------------------------------
>
> Key: JCR-934
> URL: https://issues.apache.org/jira/browse/JCR-934
> Project: Jackrabbit
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Xiaohua Lu
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.