[ARTEMIS-4785] Isolate broker run command Log4j and profile config from other CLI commands

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.33.0
• Fix Version/s: 2.37.0
• Component/s: Configuration
• Assignee: Domenico Francesco Bruscino
• Reporter: Gary Tully
• Created: 29/May/24 11:26
• Updated: 15/Aug/24 12:26
• Resolved: 15/Aug/24 12:26

Description

Isolate the broker 'run' command Log4j and profile from the other CLI commands, such that the logging configs dont interfere with each others execution, and other commands can be conigured differently than the run command.

See also sub-tasks: ARTEMIS-4702 and ARTEMIS-4974

 

Original description:
=================

I have come across a strange issue where the root cause is the instance dir cli sharing the log4j config with the broker.

the logging has a rolling file appender schedual of 1 minute. looks to be working fine, then use instance-dir/bin/artemis produicer --user invalid to generate logging... and the broker appender gets borked.

The problem, the cli is reading the same log4j2 config from the etc dir on the classpath.

This is not ideal.
One workaroud is to use the installation dir artemis for producer!consumer commands.

I wonder if we should use -Dlog4j.configuration to specify a file not on the classpath for the broker. and leave etc off the classpath?

I guess there are a few ways to solve this. but there is indeed a gotcha here.

thoughts?

Issue Links

• relates to: ARTEMIS-4702 Add utility profile for CLI commands other than run
• links to: GitHub Pull Request #5127
• links to: GitHub Pull Request #5136

Sub-Tasks

• Add utility profile for CLI commands other than run: Closed
• Disable run from the Shell: Closed