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 (JIRA)" <ji...@apache.org> on 2008/08/28 20:14:46 UTC

[jira] Closed: (SLING-497) Keep order of jobs when executing

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

Carsten Ziegeler closed SLING-497.
----------------------------------

    Resolution: Fixed

If an own job queue is used, an additional property can be specified which preserves the order of execution.
The first job is retried until it fails (too many retries), if the retries is configured as unlimited, only the first job is executed (until it is cancelled)

> Keep order of jobs when executing
> ---------------------------------
>
>                 Key: SLING-497
>                 URL: https://issues.apache.org/jira/browse/SLING-497
>             Project: Sling
>          Issue Type: New Feature
>          Components: Event
>    Affects Versions: Extensions Event 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Extensions Event 2.0.4
>
>
> Usually jobs are executed in random manner (usually first one, first out), but especially in a cluster this might not be true.
> For some jobs it might be interesting to keep the order of execution.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.