You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Clebert Suconic (Jira)" <ji...@apache.org> on 2024/08/06 19:11:00 UTC

[jira] [Commented] (ARTEMIS-4785) log4j config from classpath and cli issue

    [ https://issues.apache.org/jira/browse/ARTEMIS-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871451#comment-17871451 ] 

Clebert Suconic commented on ARTEMIS-4785:
------------------------------------------

[~brusdev] I made ARTEMIS-4785 a sub task of this JIRA. 

note to self / us: Lets make sure we mention that Run is not available any more on Shell on the release notes (versions.adoc). I was going to add a note now but it felt weird adding the note without ARTEMIS-4785 completed first.

> 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
>  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-unsubscribe@activemq.apache.org
For additional commands, e-mail: issues-help@activemq.apache.org
For further information, visit: https://activemq.apache.org/contact