You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2021/12/26 14:00:00 UTC
[jira] [Resolved] (LOG4J2-3256) Reduce ignored package scope of KafkaAppender
[ https://issues.apache.org/jira/browse/LOG4J2-3256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary D. Gregory resolved LOG4J2-3256.
-------------------------------------
Fix Version/s: 2.17.1
Resolution: Fixed
[~dongjin]
I modified GitHub patch #640 and pushed patches to branches {{release-2.x}} and {{{}master{}}}.
You are credited in {{{}changes.xml{}}}.
Thank you for your help!
G
> Reduce ignored package scope of KafkaAppender
> ---------------------------------------------
>
> Key: LOG4J2-3256
> URL: https://issues.apache.org/jira/browse/LOG4J2-3256
> Project: Log4j 2
> Issue Type: Improvement
> Reporter: Dongjin Lee
> Assignee: Gary D. Gregory
> Priority: Major
> Fix For: 2.17.1
>
>
> As of present, KafkaAppender ignores logging messages from the loggers starting with "org.apache.kafka". This is because KafkaAppender uses KafkaPoducer internally and to avoid recursive logging.
> However, the current ignored package scope, "org.apache.kafka", is too large, since KafkaProducer uses "org.apache.kafka.common" and "org.apache.kafka.client" only. It is problematic when Apache Kafka uses log4j2 for its logging.
> As of present, Apache Kafka is still using log4j 1.x, but a migration project is under-progress:
> * KAFKA-9366
> * KAFKA-12399
> If this project is taken, Apache Kafka will deprecate its log4j-appender and migrate into log4j2's KafkaAppender. Reducing the ignored package scope is a prior task to this work.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)