Re: log4j2 issue

If you don't care about old log messages that haven't been published yet between times of Kafka availability, then yeah, discarding old messages like that is an interesting workaround. On 17 March 2017 at 08:58, Mikael Ståldal wrote: > Have you tried to set

Re: log4j2 issue

Have you tried to set blocking="false" on the AsyncAppender you have around KafkaAppender? Have you tried using the system properties log4j2.AsyncQueueFullPolicy and log4j2.DiscardThreshold? https://logging.apache.org/log4j/2.x/manual/configuration.html#log4j2.AsyncQueueFullPolicy On Tue, Mar

Re: How to reload a programmed log4j2 configuration in java

I go it: import java.nio.file.Paths; import org.apache.logging.log4j.Level; import org.apache.logging.log4j.LogManager; import org.apache.logging.log4j.Logger; import org.apache.logging.log4j.core.Appender; import org.apache.logging.log4j.core.LoggerContext; import