You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Robbie Gemmell (Jira)" <ji...@apache.org> on 2022/02/11 09:33:00 UTC

[jira] [Updated] (AMQ-7426) Upgrade to log4j2

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

Robbie Gemmell updated AMQ-7426:
--------------------------------
    Description: 
This JIRA will upgrade 5.17.x to use Log4J 2.x instead of 1.x


(5.16.x was switched to using [reload4j|https://reload4j.qos.ch/] instead of Log4j 1.x via AMQ-8472 in 5.16.4)

> Upgrade to log4j2
> -----------------
>
>                 Key: AMQ-7426
>                 URL: https://issues.apache.org/jira/browse/AMQ-7426
>             Project: ActiveMQ
>          Issue Type: Task
>          Components: Broker
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.17.0
>
>          Time Spent: 4h 20m
>  Remaining Estimate: 0h
>
> This JIRA will upgrade 5.17.x to use Log4J 2.x instead of 1.x
> (5.16.x was switched to using [reload4j|https://reload4j.qos.ch/] instead of Log4j 1.x via AMQ-8472 in 5.16.4)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)