Classification: For internal use only
LoggerConfigAdmin mbean instances only exist for explicitly configured
loggers - so you can only change the level for loggers originally defined
in your config file - not for an arbitrary class or package - which I've
found a useful feature.
I've updated
Is this not what you're looking for?
http://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/jmx/LoggerConfigAdminMBean.html
On 6 August 2014 22:44, Matt Sicker boa...@gmail.com wrote:
I may take a look at this soon as I've been getting into JMX lately at
work in
Hi,
Is there any plan to merge this patch to the main branch? This
functionality seems extremely useful when modifying config file is not an
option.
Thanks,
Ang
On 6/25/14, 12:19 AM, Phil Wray phil.w...@db.com wrote:
Classification: For internal use only
Hey Ralph.
Sure - have created:
I wouldn’t have asked for a patch submission if I didn’t plan to consider it.
That said, we are all volunteers here and sometimes don’t get to things as
quickly as we would like.
Ralph
On Aug 6, 2014, at 1:24 PM, Ang Xu a...@linkedin.com.INVALID wrote:
Hi,
Is there any plan to merge this
Classification: For internal use only
Hey Ralph.
Sure - have created:
LOG4J2-681 Add ability to change log level for any class/package
dynamically via jmx
cheers,
Phil
From:
Ralph Goers rgo...@apache.org
To:
Log4J Users List log4j-user@logging.apache.org,
Date:
24/06/2014 15:34
Subject:
