[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:
causality
caused by MGNLSCH-57 CommandJob should not depend on UI (v... Closed
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 MGNLSCH-57, we removed CommandJob's method #logAndSendErrorMessage—rightfully, we removed the UI/Pulse dependency from it.

However we don't log command errors anymore (was in that method), but just rethrow the JobExecutionException.
The quartz scheduler (JobRunShell) logs it as INFO, whereas our log4j config has only WARN prio for everything under the org category.

2 solutions:
A. Reintroduce error logging from our CommandJob
B. Tune org.quartz category to INFO in magnolia-empty-webapp/src/main/webapp/WEB-INF/config/default/log4j.xml (and move this ticket to MGNLCE).

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


Generated at Mon Feb 12 10:45:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.