You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/02/16 13:59:08 UTC

[jira] Updated: (SLING-132) Auto-reconnect to the JCR Repository if it is not found or lost

     [ https://issues.apache.org/jira/browse/SLING-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated SLING-132:
------------------------------------

    Component/s:     (was: microsling)
                 Resource
    Description: 
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.

  was:
Setting the component to "microsling" as I haven't checked how that's handled in Sling.

It'd be useful to try to reconnect to the Repository from time to time, if it was not found or lost.

At startup, for example, if the Repository is provided by another webapp it might not be immediately available, but might come up after a few seconds.


> 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: Resource
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> 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.