You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/09/20 17:37:00 UTC

[jira] [Work logged] (ARTEMIS-4002) Allow $ARTEMIS_LOGGING_CONF override by respecting pre-existing value in artemis script

     [ https://issues.apache.org/jira/browse/ARTEMIS-4002?focusedWorklogId=810462&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-810462 ]

ASF GitHub Bot logged work on ARTEMIS-4002:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Sep/22 17:36
            Start Date: 20/Sep/22 17:36
    Worklog Time Spent: 10m 
      Work Description: gemmellr commented on PR #4223:
URL: https://github.com/apache/activemq-artemis/pull/4223#issuecomment-1252688752

   I didnt notice you raised a PR for this when commenting on the JIRA.
   
   I dont think we should expose the env variable with the current JBL config in use and then transition it to the Log4J 2 config later.
   
   Per the JIRA the new-logging bits already removed this entirely, making the scripts (and service related files, which this change doesnt update to use the env variable similarly but may need to?) have no knowledge of the logging.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 810462)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>
>          Time Spent: 10m
>  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)