[
https://issues.apache.org/jira/browse/LOG4J2-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carter Kozak closed LOG4J2-2658.
Verified by [~Christopher Roscoe] on 2.12.1-SNAPSHOT.
> Exceptions during compacting in the context o
[
https://issues.apache.org/jira/browse/LOG4J2-2656?focusedWorklogId=280500&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280500
]
ASF GitHub Bot logged work on LOG4J2-2656:
--
Author: ASF GitHub Bot
carterkozak commented on issue #292: LOG4J2-2656: Add support of
ignoreKafkaConnectionError flag
URL: https://github.com/apache/logging-log4j2/pull/292#issuecomment-513866416
A workaround might be to use a RoutingAppender with a single default route
of the KafkaAppender defined in place. T
[
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
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
[
https://issues.apache.org/jira/browse/LOG4J2-2656?focusedWorklogId=280452&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280452
]
ASF GitHub Bot logged work on LOG4J2-2656:
--
Author: ASF GitHub Bot
carterkozak commented on issue #292: LOG4J2-2656: Add support of
ignoreKafkaConnectionError flag
URL: https://github.com/apache/logging-log4j2/pull/292#issuecomment-513832609
It feels a bit odd for the Kafka appender to work differently from other
appenders when creation fails. I wonder if
rgoers commented on issue #292: LOG4J2-2656: Add support of
ignoreKafkaConnectionError flag
URL: https://github.com/apache/logging-log4j2/pull/292#issuecomment-513823442
I am continuing to think about this as I am not sure if this is the right
way to fix the problem.
-
[
https://issues.apache.org/jira/browse/LOG4J2-2656?focusedWorklogId=280444&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-280444
]
ASF GitHub Bot logged work on LOG4J2-2656:
--
Author: ASF GitHub Bot
[
https://issues.apache.org/jira/browse/LOG4J2-2658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890190#comment-16890190
]
Christopher Roscoe commented on LOG4J2-2658:
[~ckozak] I tested with the 2.1
[
https://issues.apache.org/jira/browse/LOG4J2-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890182#comment-16890182
]
Gary Gregory commented on LOG4J2-2660:
--
The fix I applied simply retries once. I mi
[
https://issues.apache.org/jira/browse/LOG4J2-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-2660.
--
Resolution: Fixed
Fix Version/s: 2.12.1
3.0.0
> Retry when JDBC thro
12 matches
Mail list logo