[MGNLSCH-65] Exceptions in scheduled jobs are not logged anymore Created: 20/Jun/16 Updated: 30/Jun/16 Resolved: 29/Jun/16 |
|
| Status: | Closed |
| Project: | Scheduler |
| Component/s: | None |
| Affects Version/s: | 2.2.1 |
| Fix Version/s: | 2.2.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | logging, quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Sprint: | Saigon 50 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
In However we don't log command errors anymore (was in that method), but just rethrow the JobExecutionException. 2 solutions: PS: btw, scheduler is rather greedy on logging, what you expect as info actually comes as debug, so option B. wouldn't be more verbose, besides some init messages upon startup |