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 
events will be written, right?
That means that only events of type Info, debug and trace could be lost, but 
none of the higher levels like error, warn and severe, right?

Kind regards,

On 22.12.17, 01:53, "Remko Popma" <remko.po...@gmail.com> wrote:

    Yes by default the application thread will block until a slot becomes 
available in the queue. 
    Yes this is configurable: see 
    (Shameless plug) Every java main() method deserves 
    > On Dec 20, 2017, at 2:03, Fröstl, Christian 
<christian.froe...@accenture.com> wrote:
    > 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 messages be dropped?
    > Is this a configurable behaviour?
    > Kind regards,
    > Christian
    > ________________________________
    > This message is for the designated recipient only and may contain 
privileged, proprietary, or otherwise private information. If you have received 
it in error, please notify the sender immediately and delete the original. Any 
other use of the email by you is prohibited.

To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org

Reply via email to