[
https://issues.apache.org/jira/browse/SLING-7756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-7756.
------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-event/commit/7289daeaef867e00bfb442de35d9c6f4c2ee554a.
[~indra2gurjar] Thanks a lot for your contribution.
Slightly adjusted the message in
https://github.com/apache/sling-org-apache-sling-event/commit/353631f97592787116e9db47d102641ec5461df8.
> Improve logging for Job retries
> -------------------------------
>
> Key: SLING-7756
> URL: https://issues.apache.org/jira/browse/SLING-7756
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Event 4.2.10
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> 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
(v7.6.3#76005)
