You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andrew Khoury (Jira)" <ji...@apache.org> on 2023/04/17 23:14:00 UTC

[jira] [Updated] (SLING-11831) Allow setting job properties for custom job state

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

Andrew Khoury updated SLING-11831:
----------------------------------
    Fix Version/s:     (was: Event 4.2.18)

> Allow setting job properties for custom job state
> -------------------------------------------------
>
>                 Key: SLING-11831
>                 URL: https://issues.apache.org/jira/browse/SLING-11831
>             Project: Sling
>          Issue Type: Improvement
>          Components: Event
>    Affects Versions: Event 4.2.10
>            Reporter: Andrew Khoury
>            Assignee: Konrad Windszus
>            Priority: Major
>
> Currently a {{JobConsumer}} returning {{JobResult.FAILED}} is usually retried (https://sling.apache.org/documentation/bundles/apache-sling-eventing-and-job-handling.html). Unfortunately this is not exposed in the logs, so in case a JobConsumer logs an error before returning {{JobResult.FAILED}} the job is silently retried without any particular log message. I think each failed job should lead to a WARN in the log (in case the job is retried) with the attempt number and outstanding attempts in the log message. In case a job is not retried, an ERROR should be emitted to the log for every failed job.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)