You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Gary Tully (Jira)" <ji...@apache.org> on 2022/10/14 10:35:00 UTC

[jira] [Updated] (ARTEMIS-4002) Support env $JAVA_OPTS_APPEND to override by appending to the java command used by the scripts

     [ https://issues.apache.org/jira/browse/ARTEMIS-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated ARTEMIS-4002:
--------------------------------
    Summary: Support env $JAVA_OPTS_APPEND to override by appending to the java command used by the scripts  (was: Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in artemis script)

> 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: 50m
>  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)