Gary Tully created ARTEMIS-4785:
-----------------------------------
Summary: log4j config from classpath and cli issue
Key: ARTEMIS-4785
URL: https://issues.apache.org/jira/browse/ARTEMIS-4785
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Configuration
Affects Versions: 2.33.0
Reporter: Gary Tully
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?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
