[MGNLSCH-76] CommandJob does not properly report name and catalog on exceptions Created: 08/Sep/20  Updated: 11/Sep/20  Resolved: 10/Sep/20

Status: Closed
Project: Scheduler
Component/s: None
Affects Version/s: 2.3.4
Fix Version/s: 2.3.5

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Richard Gange
Resolution: Fixed Votes: 0
Labels: maintenance, quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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: Maintenance 24
Story Points: 0.5

 Description   

When an exception occurs in the class CommandJob then eventually it should log the command and catalog.

Current Output

Cannot execute command {0}-{1}.

Expected Output

Cannot execute command website-publish

Solution
Combine

String errorMessage = String.format("Cannot execute command {0}-{1}.", cmdName, catalogName);
log.error(errorMessage, e);

into

log.error("Cannot execute command {}-{}", cmdName, catalogName, e);

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