[
https://issues.apache.org/jira/browse/JCR-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominique Pfister resolved JCR-927.
-----------------------------------
Resolution: Fixed
Thank you Hemanta for reporting this bug and providing a patch to fix it. Since
unconditionally reestablishing the connection and reexecuting a statement on an
SQL failure may lead to errors/inconsistencies, I took a more defensive
approach (see my comment above).
I added two overridables, called init() and getConnection() that may be used in
a derived class to return a connection obtained from a datasource.
Fixed in revision 541253.
> DatabaseJournal needs connection reestablishment logic
> ------------------------------------------------------
>
> Key: JCR-927
> URL: https://issues.apache.org/jira/browse/JCR-927
> Project: Jackrabbit
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.3
> Reporter: Hemanta Gupta
> Assigned To: Dominique Pfister
> Priority: Minor
> 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.
