[FINERACT-858] Errors (JobExecutionException) in Cron Jobs loose exception root cause details

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Component/s: Job Scheduler
• Assignee: Michael Vorburger
• Reporter: Michael Vorburger
• Created: 08/Mar/20 21:24
• Updated: 21/May/20 21:56
• Resolved: 21/May/20 21:56

Description

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).

Issue Links

• blocks: FINERACT-859 Optimistic locking errors were detected when flushing to the data store
• blocks: FINERACT-922 Improve SchedulerJobHelper to be more reliable and prevent flaky tests
• links to: GitHub Pull Request #727
• links to: GitHub Pull Request #855