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/07/02 14:13:45 UTC

[jira] Created: (SLING-561) Concurrent check for jobs is not working

Concurrent check for jobs is not working
----------------------------------------

                 Key: SLING-561
                 URL: https://issues.apache.org/jira/browse/SLING-561
             Project: Sling
          Issue Type: Bug
          Components: Event
    Affects Versions: Extensions Event 2.0.2
            Reporter: Carsten Ziegeler
            Assignee: Carsten Ziegeler
            Priority: Critical


The QuartzJobExecutor uses a boolean to detect if a scheduled job is running concurrently. Unfortunately on each invocation a new data map is passed into the executor and therefore the check does not work

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


[jira] Closed: (SLING-561) Concurrent check for jobs is not working

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-561.
----------------------------------

    Resolution: Fixed

> Concurrent check for jobs is not working
> ----------------------------------------
>
>                 Key: SLING-561
>                 URL: https://issues.apache.org/jira/browse/SLING-561
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons Scheduler
>    Affects Versions: Commons Scheduler 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: Commons Scheduler 2.0.4
>
>
> The QuartzJobExecutor uses a boolean to detect if a scheduled job is running concurrently. Unfortunately on each invocation a new data map is passed into the executor and therefore the check does not work

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


[jira] Updated: (SLING-561) Concurrent check for jobs is not working

Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SLING-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler updated SLING-561:
-----------------------------------

          Component/s:     (was: Event)
                       Commons Scheduler
    Affects Version/s:     (was: Extensions Event 2.0.2)
                       Commons Scheduler 2.0.2
        Fix Version/s: Commons Scheduler 2.0.4

Correct component/version

> Concurrent check for jobs is not working
> ----------------------------------------
>
>                 Key: SLING-561
>                 URL: https://issues.apache.org/jira/browse/SLING-561
>             Project: Sling
>          Issue Type: Bug
>          Components: Commons Scheduler
>    Affects Versions: Commons Scheduler 2.0.2
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Critical
>             Fix For: Commons Scheduler 2.0.4
>
>
> The QuartzJobExecutor uses a boolean to detect if a scheduled job is running concurrently. Unfortunately on each invocation a new data map is passed into the executor and therefore the check does not work

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