Just a follow up on this, do we have replacement for
"LogManager.resetConfiguration" in log4j2?
On Sat, Mar 18, 2023 at 11:27 AM Viraj Jasani wrote:
> Ah looks like monitorinterval is supported as per the doc[1]:
> Properties configuration files support the advertiser, monitorInterval,
> name,
I believe we can use "Configurator.reconfigure(uri)", however just wanted
to make sure if this is the only right way (stable API).
On Tue, Mar 21, 2023 at 4:57 PM Viraj Jasani wrote:
> Just a follow up on this, do we have replacement for
> "LogManager.resetConfiguration" in log4j2?
>
>
> On Sat
Actually, Configurator.reconfigure() will cause the existing configuration
(file or uri) to be reloaded. You would use it with the uri or configuration
parameter if you want to load a new configuration.
Ralph
> On Mar 21, 2023, at 5:48 PM, Viraj Jasani wrote:
>
> I believe we can use "Configu
Thanks a lot, Ralph!
Let me ask one more question. For any further questions, I would create a
new mail thread.
We also have a utility in hadoop that tries to add FileAppender at runtime,
and also change the threshold of all appenders from root level. Is this
doable with log4j2? I could not find A
Yes, it is doable. That said, there are almost always better ways to implement
whatever your “real” requirement is.
Looking at what that code is doing it is just enabling logging to a file at a
level for some time period. Instead, you can just create the Appender in your
configuration and conf