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

Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/08/29 13:14:20 UTC

[jira] [Updated] (SLING-6013) Clarify queue.maxparallel handling for ordered queues

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

Konrad Windszus updated SLING-6013:
-----------------------------------
    Component/s: Extensions

> Clarify queue.maxparallel handling for ordered queues
> -----------------------------------------------------
>
>                 Key: SLING-6013
>                 URL: https://issues.apache.org/jira/browse/SLING-6013
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Trivial
>
> Neither from the OSGi configuration description of job queues nor from the documentation at http://sling.staging.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html#queue-configurations it is obvious that {{queue.maxparallel}} is always set to 1 for ordered queues.
> See also http://apache-sling.73963.n3.nabble.com/Sling-Jobs-Ordered-Queue-and-configuration-queue-maxparallel-td4064295.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)