[
https://issues.apache.org/jira/browse/AMQ-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493167#comment-17493167
]
Robbie Gemmell commented on AMQ-7426:
-------------------------------------
The Log4J transitive dependency from Zookeeper related bits were excluded
(directly or via dependencyManagement) and reload4j was added to
activemq-partition as a dependency to serve in their place during AMQ-8472. The
classes included in activemq-all thus should be those from {_}reload4j{_},
which necessarily uses the same _org.apache.log4j_ namespace to serve their
intent to act as a substitute for Log4j. The
/META-INF/maven/ch.qos.reload4j/reload4j/ presence in the
activemq-all-5.16.4.jar file without a log4j equivalent (such as the
/META-INF/maven/log4j/log4j/ present in 5.16.3) further suggests that is indeed
the case. It should be trivial to confirm that either way by simply comparing
the actual contained classes with those from the individual reload4j/log4j jars.
(Aside: easier still, dont use activemq-all, use the specific components you
need and maintain visibility and control of what is actually being utilised)
> 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)
