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 2010/02/18 09:44:27 UTC
[jira] Created: (SLING-1389) Background loading might not load all
stored jobs
Background loading might not load all stored jobs
-------------------------------------------------
Key: SLING-1389
URL: https://issues.apache.org/jira/browse/SLING-1389
Project: Sling
Issue Type: Bug
Affects Versions: Extensions Event 2.2.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Extensions Event 2.2.2
The current background loading introduced with 2.2.0 loads jobs in batches and uses the created date as an identifier. However if there are several jobs with the same created date, some jobs might not be loaded from the repository in rare circumstances.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-1389) Background loading might not load all
stored jobs
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-1389:
------------------------------------
Component/s: Extensions
> Background loading might not load all stored jobs
> -------------------------------------------------
>
> Key: SLING-1389
> URL: https://issues.apache.org/jira/browse/SLING-1389
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 2.2.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.2.2
>
>
> The current background loading introduced with 2.2.0 loads jobs in batches and uses the created date as an identifier. However if there are several jobs with the same created date, some jobs might not be loaded from the repository in rare circumstances.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1389) Background loading might not load all
stored jobs
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1389.
-----------------------------------
> Background loading might not load all stored jobs
> -------------------------------------------------
>
> Key: SLING-1389
> URL: https://issues.apache.org/jira/browse/SLING-1389
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Extensions Event 2.2.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.3.0
>
>
> The current background loading introduced with 2.2.0 loads jobs in batches and uses the created date as an identifier. However if there are several jobs with the same created date, some jobs might not be loaded from the repository in rare circumstances.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1389) Background loading might not load all
stored jobs
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1389.
-------------------------------------
Resolution: Fixed
Added a loop which loads all events with the last loaded creation time to avoid this problem. Refactored the job loading code.
Changed in revision: 911855
> Background loading might not load all stored jobs
> -------------------------------------------------
>
> Key: SLING-1389
> URL: https://issues.apache.org/jira/browse/SLING-1389
> Project: Sling
> Issue Type: Bug
> Affects Versions: Extensions Event 2.2.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.2.2
>
>
> The current background loading introduced with 2.2.0 loads jobs in batches and uses the created date as an identifier. However if there are several jobs with the same created date, some jobs might not be loaded from the repository in rare circumstances.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.