R/
Alberto
De: Kirk Lund
Enviado: miércoles, 8 de abril de 2020 18:27
Para: geode
Asunto: Re: About "change loglevel" command
This behavior has always worked like this since the internal implementation
of logging changed from GemFire LogWriters to us
was started
> using the '--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS' system property."
>
> BR/
>
> Alberto B.
>
>
>
>
> ________
> De: Kirk Lund
> Enviado: martes, 7 de abril de 2020 0:17
> Para: geode
> Asunto: Re: Abou
nge was started using the
'--J=-Dgeode.LOG_LEVEL_UPDATE_OCCURS=ALWAYS' system property."
BR/
Alberto B.
De: Kirk Lund
Enviado: martes, 7 de abril de 2020 0:17
Para: geode
Asunto: Re: About "change loglevel" command
Yes, this behavior
Yes, this behavior is correct. If the User provides their own logging
configuration (or a different logging impl such as logback) then none of
the log-* configuration properties in Geode have any effect.
On Mon, Apr 6, 2020 at 9:26 AM Alberto Bustamante Reyes
wrote:
> Hi all,
>
> I have observed
Hi all,
I have observed that "change loglevel" command doesn't work if the "log4j2.xml"
file used doesn't contain the "geode-default" property set to true. This
requirement is not documented [1], so I would like to confirm if this is the
correct behavior.
If we add "geode-default=true" in our
