[
https://issues.apache.org/jira/browse/ARTEMIS-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17607125#comment-17607125
]
Robbie Gemmell commented on ARTEMIS-4002:
-----------------------------------------
Yes, you would need to use the logging impls configuration props to provide
your own file, rather than using the default auto-discovered config provided in
the instance etc directory.
Though you would obviously still need to know the impl-specific logging
framework in use in order to provide it any applicable configuration via such a
new (visible/configurable) environment variable, so the latter is hardly
impl-agnostic even if you then dont need to know the well-known sysprop for
setting its config file.
Right now the scripts on the new-logging branch have no knowledge of the
logging anymore, removing all the mechanics and simplifying them versus what
what was there before (which has needed patched multiple times for upgraders,
even in a bugfix release once). If they were to expose a new configurable env
variable they would need to go back to having knowledge of the logging impl and
if/when to use a provided config to set the config sysprop (which it doesnt by
default due to using auto-discovery and leaving others free to specify it if
they want).
> Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in
> artemis script
> ---------------------------------------------------------------------------------------
>
> Key: ARTEMIS-4002
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4002
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.25.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Trivial
> Fix For: 3.0.0
>
>
> We set the logging system property using an env var, however we don't allow
> that env var to be provided, it is currently overwritten
> When the env can be easily modified, it would be great to be able to easily
> provide an alternative logging file via setting the $ARTEMIS_LOGGING_CONF
> variable.
> We just have to set it only when it is empty!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
