Hi Pooja,

We faced the same problem that log4j1.x bridge does not support 
PropertyConfigurator API. See 

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


From: Gary Gregory <garydgreg...@gmail.com>
Date: Wednesday, March 9, 2022 at 5:13 AM
To: Log4J Users List <log4j-user@logging.apache.org>
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.


On Wed, Mar 9, 2022, 06:47 Pooja Pandey <pooja.pan...@asg.com.invalid>

> 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

Reply via email to