[
https://issues.apache.org/jira/browse/ARTEMIS-4002?focusedWorklogId=816959&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-816959
]
ASF GitHub Bot logged work on ARTEMIS-4002:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 14/Oct/22 11:04
Start Date: 14/Oct/22 11:04
Worklog Time Spent: 10m
Work Description: gemmellr commented on PR #4223:
URL:
https://github.com/apache/activemq-artemis/pull/4223#issuecomment-1278856394
It doesnt need to override in the logging case anymore, as the scripts dont
do anything in that regard.
Issue Time Tracking
-------------------
Worklog Id: (was: 816959)
Time Spent: 1h (was: 50m)
> Support env $JAVA_OPTS_APPEND to override by appending to the java command
> used by the scripts
> ----------------------------------------------------------------------------------------------
>
> 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: 1h
> Remaining Estimate: 0h
>
> logging was one use case, overriding jaas login.config is another. From an
> env var, be able to append values to the command line such that system
> property values can be overridden.
> There is DEBUG_ARGS - but those are good to use for debug, it is not ideal to
> set DEBUG_ARGS=-Djaas.login.config=x.y when you want to provide some explicit
> java config.
> Would JAVA_OPTS_APPEND work?
> The JDK_JAVA_ARGS can work for new bits, but because that is prepended to the
> command line, it cannot be used to override a value provided by the script.
> We add it after DEBUG_ARGS on the command line.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
