[ https://issues.apache.org/jira/browse/ARTEMIS-4785?focusedWorklogId=928874&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-928874 ]
ASF GitHub Bot logged work on ARTEMIS-4785: ------------------------------------------- Author: ASF GitHub Bot Created on: 06/Aug/24 09:26 Start Date: 06/Aug/24 09:26 Worklog Time Spent: 10m Work Description: brusdev commented on code in PR #5127: URL: https://github.com/apache/activemq-artemis/pull/5127#discussion_r1705216204 ########## artemis-cli/src/main/resources/org/apache/activemq/artemis/cli/commands/etc/artemis.profile: ########## @@ -60,4 +60,6 @@ if [ "$1" = "run" ]; then : # Uncomment for async profiler # DEBUG_ARGS="-XX:+UnlockDiagnosticVMOptions -XX:+DebugNonSafepoints" +else + JAVA_ARGS="$JAVA_ARGS -Dlog4j2.configurationFile=${ARTEMIS_INSTANCE_ETC_URI}log4j2-default.properties " Review Comment: Good point, I'll fix it. Issue Time Tracking ------------------- Worklog Id: (was: 928874) Time Spent: 50m (was: 40m) > 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: 50m > 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