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 2015/11/23 14:12:10 UTC

[jira] [Resolved] (SLING-5319) When loading a job distinguish between fatale and recoverable error

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

Carsten Ziegeler resolved SLING-5319.
-------------------------------------
    Resolution: Fixed

Solved in rev 1715799

> When loading a job distinguish between fatale and recoverable error
> -------------------------------------------------------------------
>
>                 Key: SLING-5319
>                 URL: https://issues.apache.org/jira/browse/SLING-5319
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>             Fix For: Event 4.0.0
>
>
> Currently, when a job can't be loaded, it is retried regardless of the reason why loading failed. The idea is that loading only fails if a class needed for deserializing the payload is currently not available (bundle missing). However as anything can go wrong, we should distinguish between recoverable errors and non recoverable errors and in the latter case discard the job



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