PM
To: Log4J Users List
Subject: Re: Issue after moving to log4j 2.19
This indicates that for some reason Log4j 2 is now initializing earlier -
before your system property is being set.
Your solution gets the currently configured LoggerContext (presumably using the
default configuration) and caus
uot;);
>
> this.systemLog = context.getLogger("LOGGER_SYSTEM");
>
>
> Thanks,
>
> Joan.
>
> -Original Message-
> From: Joan ventusproxy
> Sent: Monday, October 17, 2022 1:47 PM
> To: 'Log4J Users List'
> Subject: RE: Issue after moving t
ventusproxy
Sent: Monday, October 17, 2022 1:47 PM
To: 'Log4J Users List'
Subject: RE: Issue after moving to log4j 2.19
Hello,
Investigating a little more ...
If I set the variable
-Dlog4j.configurationFile=/opt/ventusproxy/app/proxy/ROOT/WEB-INF/log4j.xml on
the tomcat startup sc
lectorNamed
true
log4jContextName
ventusproxy
Thanks,
Joan.
-Original Message-
From: Joan ventusproxy
Sent: Sunday, October 16, 2022 9:03 PM
To: 'Log4J Users List'
Subject: RE: Issue after moving to log4j 2.19
Is not this? (second gist):
DEBUG Statu
ation=/opt/ventusproxy/app/proxy/ROOT/WEB-INF/log4j.xml]
Joan.
-Original Message-
From: Ralph Goers
Sent: Sunday, October 16, 2022 2:44 AM
To: Log4J Users List
Subject: Re: Issue after moving to log4j 2.19
In both of those log files Log4j is not seeing any value as being set of
log4j.configu
Hi Joan,
On Sun, 16 Oct 2022 at 00:45, Joan ventusproxy
wrote:
> The " log4j.configurationFile " variable is set in this way:
> System.setProperty("log4j.configurationFile",
> "/opt/ventusproxy/app/proxy/ROOT/WEB-INF/log4j.xml");
For some unknown reason this is executed too late (after Log4j2
c
with Apache Tomcat 8.5.39 and Oracle jdk
> 11 works perfectly, logs are created and the hazelcast logging is sent to the
> SYSTEM_LOG.
>
>
> Thanks,
>
> Joan.
>
> -Original Message-
> From: Piotr P. Karwasz
> Sent: Friday, October 14, 2
ng is sent to the
SYSTEM_LOG.
Thanks,
Joan.
-Original Message-
From: Piotr P. Karwasz
Sent: Friday, October 14, 2022 5:23 PM
To: Log4J Users List
Subject: Re: Issue after moving to log4j 2.19
Hi Joan,
> After making a lot of tests trying to get this working again, we had to
Hi Joan,
> After making a lot of tests trying to get this working again, we had to
> change the line below:
>
> this.systemLog = LogManager.getLogger("LOGGER_SYSTEM");
>
> �
>
> By this:
>
> this.systemLog = LogManager.getContext().getLogger("LOGGER_SYSTEM");
This looks like a `LoggerContextSel
Hello,
�
We have moved to log4j 2.19.0 from log4j 2.17.2. Our environment is Centos9
stream with tomcat 8.5.83 and jdk11. After doing that, logging has stopped
working (the code related to log4j2 has not been changed for years)
�
All our loggers are asynchronous by adding:
-DLog4jContextSe
10 matches
Mail list logo
