[
https://issues.apache.org/jira/browse/LOG4J2-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16312067#comment-16312067
]
Mikael Ståldal commented on LOG4J2-2162:
----------------------------------------
Reconnection, while useful, is not identical to what this ticket is about.
Reconnection could, depending on how it is implemented, also block application
startup until successful, and thus not fully address this ticket.
Reconnection is also useful for recovering from a broken connection after
successful startup, which is a different use case. However, I think that the
Kafka client library we use already does this, so maybe general reconnection
support like for socket and JMS is redundant for KafkaAppender. We should check
that before implementing that [~garydgregory].
> KafkaAppender fails application startup when bootstrap server are not
> available
> -------------------------------------------------------------------------------
>
> Key: LOG4J2-2162
> URL: https://issues.apache.org/jira/browse/LOG4J2-2162
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.8.2, 2.10.0
> Environment: Tried on Windows 10, IDE Eclipse Oxygen
> Reporter: Shwetank Sharma
> Labels: kafka, newbie
> Attachments: log4j2.xml
>
>
> When the server mentioned in bootstrap.servers property in kafka appender are
> not available.
> For e.g. Unable to resolve DNS etc.
> The application isn't starting and the java process terminates after trying
> to connect to the server.
> Failure to initialize the appender should not block the application process
> and other appenders, just like file appender, for e.g. when file path is not
> resolvable, it moves forward.
> Attached log4j2.xml.
> Tried wrapping it in async appender as well, does not provide expected result
> as the issue is with initialization of appender.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
