Re: [External] Re: Log4j2 Async logger fallback method

Can you provide some more information about your environment, to we are able to reproduce this issue? On 2018-01-16 16:50, Fröstl, Christian wrote: Hi Mikael, Unfortunately it is not working in my setup to include the log4j2.component.properties file. I am not possible at the moment to

Re: [External] Re: Log4j2 Async logger fallback method

Hi Mikael, Unfortunately it is not working in my setup to include the log4j2.component.properties file. I am not possible at the moment to configure the another asyncQueueFullPolicy. I tried the following ways: (we are using Hybris) First Try: 1. Configure the asynclogger with xml

Re: [External] Re: Log4j2 Async logger fallback method

Or include a log4j2.component.properties file in classpath. https://logging.apache.org/log4j/2.x/manual/configuration.html#System_Properties On 2018-01-03 17:57, Matt Sicker wrote: Those are system properties, but in log4j 2.10+, you can also use an environment variable instead. On 3 January

Re: [External] Re: Log4j2 Async logger fallback method

Those are system properties, but in log4j 2.10+, you can also use an environment variable instead. On 3 January 2018 at 07:36, Fröstl, Christian < christian.froe...@accenture.com> wrote: > Hi, > > Thanks, that clarifies it. ( > Is it possible to set the log4j2.asyncQueueFullPolicy and >

Re: [External] Re: Log4j2 Async logger fallback method

Hi, Thanks, that clarifies it. ( Is it possible to set the log4j2.asyncQueueFullPolicy and log4j2.discardThreshold in the log4j2 xml configuration file or only as environment variable? Greetings, Christian On 03.01.18, 09:43, "Remko Popma" wrote: No, the default

Re: [External] Re: Log4j2 Async logger fallback method

No, the default async queue full policy is to block and not drop any events. (This is different from Logback whose AsyncAppender is “lossy by default if 80% full”.) Log4j 2.10 will block until space becomes available in the buffer. If you configure the DiscardingAsyncQueueFullPolicy

Re: [External] Re: Log4j2 Async logger fallback method

Hi, Thanks for your response. Just one question to verify. In the default configuration, all events of level info, debug and trace will be dropped, if the ringbuffer is full. For all other events the application will block and if the ringbuffer has space again, the block will release and the

Re: Log4j2 Async logger fallback method

Yes by default the application thread will block until a slot becomes available in the queue. Yes this is configurable: see https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncQueueFullPolicyFactory.java (Shameless plug) Every

Log4j2 Async logger fallback method

Hi, I currently don’t find any documentation regarding the fallback methods of the log4j2 async logger. What happens when the AsyncLogger.RingBufferSize is too small to log all entries from a burst? Will the application fall back into sync logging and slow down the application or will the new