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/09/20 17:05:33 UTC
[jira] Created: (SLING-1788) Fail early if loaded job should not be
processed on the current app node
Fail early if loaded job should not be processed on the current app node
------------------------------------------------------------------------
Key: SLING-1788
URL: https://issues.apache.org/jira/browse/SLING-1788
Project: Sling
Issue Type: Improvement
Components: Extensions
Affects Versions: Extensions Event 2.4.0
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
Fix For: Extensions Event 2.4.2
Currently, if a job is marked to run local, it is first loaded and then later on discarded - the problematic part here is if the job can't be loaded due to class problems like a missing bundle etc. In this case the job is added to the unloaded jobs queue and retried later on.
This could be optimized by checking the run local property first and then immediately discarding the job
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-1788) Fail early if loaded job should not be
processed on the current app node
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-1788.
-----------------------------------
> Fail early if loaded job should not be processed on the current app node
> ------------------------------------------------------------------------
>
> Key: SLING-1788
> URL: https://issues.apache.org/jira/browse/SLING-1788
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Event 2.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.4.2
>
>
> Currently, if a job is marked to run local, it is first loaded and then later on discarded - the problematic part here is if the job can't be loaded due to class problems like a missing bundle etc. In this case the job is added to the unloaded jobs queue and retried later on.
> This could be optimized by checking the run local property first and then immediately discarding the job
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-1788) Fail early if loaded job should not
be processed on the current app node
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-1788.
-------------------------------------
Resolution: Fixed
Changed in revision 998952
> Fail early if loaded job should not be processed on the current app node
> ------------------------------------------------------------------------
>
> Key: SLING-1788
> URL: https://issues.apache.org/jira/browse/SLING-1788
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Extensions Event 2.4.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Extensions Event 2.4.2
>
>
> Currently, if a job is marked to run local, it is first loaded and then later on discarded - the problematic part here is if the job can't be loaded due to class problems like a missing bundle etc. In this case the job is added to the unloaded jobs queue and retried later on.
> This could be optimized by checking the run local property first and then immediately discarding the job
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.