[
https://issues.apache.org/jira/browse/ARTEMIS-4785?focusedWorklogId=929279&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-929279
]
ASF GitHub Bot logged work on ARTEMIS-4785:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Aug/24 06:04
Start Date: 08/Aug/24 06:04
Worklog Time Spent: 10m
Work Description: brusdev opened a new pull request, #5136:
URL: https://github.com/apache/activemq-artemis/pull/5136
The run command uses the artemis.profile and log4j2.properties files while
all other CLI commands use the artemis-utility.profile and
log4j2-default.properties files.
Issue Time Tracking
-------------------
Worklog Id: (was: 929279)
Time Spent: 1h 10m (was: 1h)
> log4j config from classpath and cli issue
> -----------------------------------------
>
> Key: ARTEMIS-4785
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4785
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.33.0
> Reporter: Gary Tully
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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: issues-unsubscr...@activemq.apache.org
For additional commands, e-mail: issues-h...@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact
