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
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
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
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
>
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
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
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