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/10/07 19:47:00 UTC

[jira] [Work logged] (ARTEMIS-4020) switch to using SLF4J for logging API and use Log4j 2 for broker distribution

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

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

                Author: ASF GitHub Bot
            Created on: 07/Oct/22 19:46
            Start Date: 07/Oct/22 19:46
    Worklog Time Spent: 10m 
      Work Description: tabish121 opened a new pull request, #4247:
URL: https://github.com/apache/activemq-artemis/pull/4247

   …cks (add some where useful)
   
   Logger statements should use formatting syntax and let the normal framework checks take care of checking if a logger is enabled instead of string concats and isXEnabled logger checks except in cases there is known expense to the specifc logging message/arg preparation or passing.
   
   Changes from myself and Robbie Gemmell.
   
   Co-authored-by: Robbie Gemmell <ro...@apache.org>




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

    Worklog Id:     (was: 814794)
    Time Spent: 7h 20m  (was: 7h 10m)

> switch to using SLF4J for logging API and use Log4j 2 for broker distribution
> -----------------------------------------------------------------------------
>
>                 Key: ARTEMIS-4020
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4020
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 2.27.0
>
>          Time Spent: 7h 20m
>  Remaining Estimate: 0h
>
> Switch to using [SLF4J|https://www.slf4j.org/] as the logging API for the code base, with end-uses supplying and configuring an SLF4J-supporting logging implementation of their choice based on their needs.
> For the client, applications will need to supply an SLF4J binding to a logging implementation of their choice to enable logging. An example of doing so using [Log4J 2|https://logging.apache.org/log4j/2.x/manual/index.html] is given in (/will be, once the release is out) the [client logging documentation|https://activemq.apache.org/components/artemis/documentation/latest/logging.html#logging-in-a-client-application].
> For the broker, the assembly distribution will include [Log4J 2|https://logging.apache.org/log4j/2.x/manual/index.html] as its logging implentation, with the "artemis create" CLI command used to create broker instances now creating a log4j2.properties configuration within the <broker-instance>/etc/ directory to configure Log4J. Details for upgrading an existing broker-instance is given in (/will be, once the release is out) the [version upgrade documentation|https://activemq.apache.org/components/artemis/documentation/latest/versions.html].



--
This message was sent by Atlassian Jira
(v8.20.10#820010)