[
https://issues.apache.org/jira/browse/SLING-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved SLING-132.
-------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Felix Meschberger
I consider this issue fixed after the recent checkins and minor fix due to
SLING-310.
Please close if it fixes your issue. Thanks.
> Auto-reconnect to the JCR Repository if it is not found or lost
> ---------------------------------------------------------------
>
> Key: SLING-132
> URL: https://issues.apache.org/jira/browse/SLING-132
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: 2.0.0
>
>
> Affects the jackrabbit-client bundle accessing a "remote" repository.
> Currently the respective component just tries to access the repository and
> gives up, if it fails.
> This should be enhanced to:
> * retry in configurable intervals whether the repository is now available
> * find out that a repository may have gone and try to reconnect in the
> same configurable intervals
> Care must be taken in the second case to drop (close ?) any sessions still
> connected with the old disappeared repository.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
