[
https://issues.apache.org/jira/browse/LOG4J2-2656?focusedWorklogId=280498&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280498
]
ASF GitHub Bot logged work on LOG4J2-2656:
------------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jul/19 16:51
Start Date: 22/Jul/19 16:51
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #292: LOG4J2-2656: Add
support of ignoreKafkaConnectionError flag
URL: https://github.com/apache/logging-log4j2/pull/292#issuecomment-513864473
@carterkozak The AppenderControl already wraps Appenders to catch the
exceptions they throw. There is already a generic way to cause it to stop
suppressing the exceptions that are thrown while it is executing. But off the
top of my head I don't recall if there is a standard way to handle exceptions
while the Appender is created. Most of the ones I have seen just the Appender
to be null, but other stuff still may succeed.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 280498)
Time Spent: 0.5h (was: 20m)
> Add possibility to ignore exception if kafka connection error occurred
> ----------------------------------------------------------------------
>
> Key: LOG4J2-2656
> URL: https://issues.apache.org/jira/browse/LOG4J2-2656
> Project: Log4j 2
> Issue Type: Improvement
> Components: Appenders
> Affects Versions: 2.12.0
> Reporter: Artyom Krikheli
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Nowadays if we use a log4j2-Kafka-appender with Spring Boot framework and
> Kafka is unavailable for some reason, the application crashes. We may have
> several appenders (File appender, SYSOUT, etc) and I think that Kafka's
> inaccessibility is not a reason for the failure of an application.
> {code:java}
> Caused by: org.apache.kafka.common.KafkaException: Failed to construct kafka
> producer at
> org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:457)
> at
> org.apache.kafka.clients.producer.KafkaProducer.<init>(KafkaProducer.java:304)
> at
> org.apache.logging.log4j.core.appender.mom.kafka.DefaultKafkaProducerFactory.newKafkaProducer(DefaultKafkaProducerFactory.java:40)
> at
> org.apache.logging.log4j.core.appender.mom.kafka.KafkaManager.startup(KafkaManager.java:131)
> at
> org.apache.logging.log4j.core.appender.mom.kafka.KafkaAppender.start(KafkaAppender.java:175)
> at
> org.apache.logging.log4j.core.config.AbstractConfiguration.start(AbstractConfiguration.java:266)
> at
> org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:547)
> at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:263)
> at
> org.springframework.boot.logging.log4j2.Log4J2LoggingSystem.loadConfiguration(Log4J2LoggingSystem.java:175)
> {code}
> I can offer to add a special boolean property to logger config named
> *ignoreKafkaConnectionError* and in depends on its value we can either catch
> kafka exceptions occurred while producer creating or not.
> I have implemented this feature and have opened the pull request:
> [https://github.com/apache/logging-log4j2/pull/292]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
