[
https://issues.apache.org/jira/browse/ARTEMIS-4002?focusedWorklogId=816946&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-816946
]
ASF GitHub Bot logged work on ARTEMIS-4002:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Oct/22 10:32
Start Date: 14/Oct/22 10:32
Worklog Time Spent: 10m
Work Description: gtully commented on PR #4223:
URL:
https://github.com/apache/activemq-artemis/pull/4223#issuecomment-1278819776
we can close this. the problem still exists, how to easily override an value
on the command line for the artemis java command wih an env var. I noticed
this one for logging and it fits the bill in that case. and was a quick win.
There is $DEBUG_ARGS but I think we may need JAVA_OPTS_APPEND, the
$JDK_JAVA_ARGS does prepend so it cannot override.
Issue Time Tracking
-------------------
Worklog Id: (was: 816946)
Time Spent: 40m (was: 0.5h)
> 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: 2.27.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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)
