You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/05/09 01:06:00 UTC
[jira] [Updated] (FINERACT-858) Errors (JobExecutionException) in
Cron Jobs loose exception rot cause details
[ https://issues.apache.org/jira/browse/FINERACT-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Vorburger updated FINERACT-858:
---------------------------------------
Component/s: Job Scheduler
> Errors (JobExecutionException) in Cron Jobs loose exception rot cause details
> -----------------------------------------------------------------------------
>
> Key: FINERACT-858
> URL: https://issues.apache.org/jira/browse/FINERACT-858
> Project: Apache Fineract
> Issue Type: Bug
> Components: Job Scheduler
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The way that the {{@CronTarget}} annotated cron job methods {{catch (Exception e)}} and then do {{throws JobExecutionException}} looses the root cause(s). This makes fully understanding and debugging e.g. (one of) the problem shown in FINERACT-857, for a solution like FINERACT-859, more difficult.
> I'll try to fix this in this issue (just the error logging, not the actual problem).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)