Here is our code snippet:
public void configure(URL configURL) {
System.setProperty(ConfigurationFactory.LOG4J1_CONFIGURATION_FILE_PROPERTY,
configURL.toString());
System.clearProperty(LOG4J1_MONITOR_INTERVAL);
LoggerContext context = LoggerContext.getContext(false);
context.setConfigLocation(null);
}
-Jason
From: Pooja Pandey <[email protected]>
Date: Wednesday, March 9, 2022 at 7:50 PM
To: Log4J Users List <[email protected]>
Subject: RE: [External Sender] Re: Alternative to PropertyConfigurator while
migrating from log4j1.x to log4j1.x bridge
Hi Jason,
-> Our solution is to use log4j2 api to implement what
PropertyConfigurator.configure does.
Can you please share the solution snippet for reference?
Thanks,
Pooja
-----Original Message-----
From: Jason Wen <[email protected]>
Sent: Wednesday, March 9, 2022 9:16 PM
To: Log4J Users List <[email protected]>
Subject: Re: [External Sender] Re: Alternative to PropertyConfigurator while
migrating from log4j1.x to log4j1.x bridge
*** External email: Verify sender before opening attachments or links ***
Hi Pooja,
We faced the same problem that log4j1.x bridge does not support
PropertyConfigurator API. See
https://logging.apache.org/log4j/2.x/manual/migration.html
#### Limitations of the Log4j 1.x bridge
Applications can migrate by just using the bridge without further code changes,
if they meet the following requirements:
1. They must not access methods and classes internal to the Log4j 1.x
implementation such as Appenders, LoggerRepository or Category's callAppenders
method.
2. They must not programmatically configure Log4j.
3. They must not configure by calling the Log4j 1.x classes DOMConfigurator
or PropertyConfigurator.
Our solution is to use log4j2 api to implement what
PropertyConfigurator.configure does.
Thanks,
Jason
From: Gary Gregory <[email protected]>
Date: Wednesday, March 9, 2022 at 5:13 AM
To: Log4J Users List <[email protected]>
Subject: [External Sender] Re: Alternative to PropertyConfigurator while
migrating from log4j1.x to log4j1.x bridge Hello Pooja,
Please describe exactly what is happening. The information provided in too
vague. I take it from previous messages that you are using Log4j 2.17.2 jars
and that there are no Log4j 1 jars on your class path? A reproduced would be
best, preferably as a failing test in a GitHub PR. Otherwise, there is no way
for us to tell what your are doing.
Ty,
Gary
On Wed, Mar 9, 2022, 06:47 Pooja Pandey <[email protected]>
wrote:
> We are using PropertyConfigurator.configure(), but this doesn't work
> in log4j1.x bridge.
>
>
>
> Please let me know if you have any idea on how to fix it.
>
>
>
> Thanks,
>
> Pooja
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
