You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2022/06/06 13:31:00 UTC
[jira] [Assigned] (SLING-11379) Do not create duplicate scheduled jobs
[ https://issues.apache.org/jira/browse/SLING-11379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joerg Hoh reassigned SLING-11379:
---------------------------------
Assignee: Joerg Hoh
> Do not create duplicate scheduled jobs
> --------------------------------------
>
> Key: SLING-11379
> URL: https://issues.apache.org/jira/browse/SLING-11379
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Event 4.3.2
> Reporter: Joerg Hoh
> Assignee: Joerg Hoh
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I came across situations where periodic jobs were added in the activation of an OSGI component, which eventually piles up to a huge amount of (identical) jobs being scheduled, causing major problems on load and stability.
> Before adding a new scheduled job, it should be checked if it already exists.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)