[
https://issues.apache.org/jira/browse/SLING-7661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474069#comment-16474069
]
indra kumar gurjar commented on SLING-7661:
-------------------------------------------
[~lnra54] JobExecutor.process method gives access to JobExecutionContext. We
can set the error message by
JobExecutionContext.result().message(errorMsg).failed() and return this result.
The error message can be retrieved by Job.getResultMessage();
> Provide mechanism to persist error message/s in Sling Jobs API
> --------------------------------------------------------------
>
> Key: SLING-7661
> URL: https://issues.apache.org/jira/browse/SLING-7661
> Project: Sling
> Issue Type: Improvement
> Components: API
> Reporter: Leonardo Rodriguez
> Priority: Minor
>
> The sling Jobs API provides a JobConsumer interface:
> org.apache.sling.event.jobs.consumer.JobConsumer" and Job interface:
> org.apache.sling.event.jobs.Job.
> Currently, when a JobConsumer fails, it's supposed to return a
> JobResult.CANCEL, but there is no way to set an error message.
> Looking at the JCR, we see that such (failed/canceled) jobs are saved to
> /var/eventing/jobs/cancelled/ with a property
> "slingevent:finishedState=ERROR".
> It would be beneficial to add a method to the Job interface to set an error
> String or List<String> for multiple errors (to save stacktrace perhaps). That
> way if a job fails we can debug the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
