[
https://issues.apache.org/jira/browse/JCR-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557641#action_12557641
]
Jukka Zitting commented on JCR-927:
-----------------------------------
I mean that when a connection is lost, then for example a getRecords() call
will first throw an exception and then work again when it is next called.
Of course, now that I traced the logic back to ClusterNode, throwing an
exception in getRecords() doesn't matter that much as ClusterNode will just log
it as an error and try again in a short while. So I guess there's nothing we
need to do.
> DatabaseJournal needs connection reestablishment logic
> ------------------------------------------------------
>
> Key: JCR-927
> URL: https://issues.apache.org/jira/browse/JCR-927
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Hemanta Gupta
> Assignee: Dominique Pfister
> Priority: Minor
> Fix For: 1.4
>
> Attachments: JNDIDatabaseJournal.java
>
>
> The DB based file system and persistence manager implementations have logic
> for connection reestablishment in case the DB server bounces while the
> repository is running, but the DB based journal implementation doesn't.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
