You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/13 10:59:30 UTC

[jira] [Resolved] (SLING-2289) Implement generic retry mechanism

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

Carsten Ziegeler resolved SLING-2289.
-------------------------------------

    Resolution: Fixed

Implemented in revision 1213634
                
> Implement generic retry mechanism
> ---------------------------------
>
>                 Key: SLING-2289
>                 URL: https://issues.apache.org/jira/browse/SLING-2289
>             Project: Sling
>          Issue Type: New Feature
>          Components: Installer
>    Affects Versions: Installer Core 3.2.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.2.4
>
>
> Currently, if a task fails it is retried over and over again which basically is kind of an endless loop.
> However, if between two retries nothing has changed, it is most likely that a retry is failing again. We have some basic code for bundle handling, but this is a) tied to bundles, b) not reusable, and c) not working perfectly.
> Instead we should come up with a generic mechanism for retries - a task should signal that it want's to be retried. In addition we need a notification mechanism which notifies the installer to retry something, e.g. a service listening for bundle events would notify the installer each time a bundle event has occurred etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira