I'm using the log4j support for JMX to do this, but it is limited to
"existing" loggers (entries in log4j.xml). If tou're familiar with JMX,
adding an MBean to get a logger and change it's level is not difficult.
www.codeczar.com also provides a web module to manage log4j.
2006/12/21, Pankaj C
I'm using it via Spring jmx this way :
class="org.apache.log4j.jmx.HierarchyDynamicMBean"/>
This gives me acces to the log4j MBeans to get existing loggers and
change levels. Please note
I do it.
I'm using the "addLoggerMBean" method to get a manageable logger
instance and then change the priority value.
I only can create MBeans for loggers that exist in the log4j.xml, so
level management looks like a simple trace ON/OFF.
Nico.
Daniel Serodio a écrit :
Did anyone manage t
To solve this I'm using a custom log4j.xml (with debugs enabled) and run
my app with
-Dlog4j.configuration=file:///D:/log4j.xml
Using this, I can configure log4j for production and have all the debugs
I need on my dev computer.
James Stauffer a écrit :
Can you keep the config file out of t
your Nullpointer is thrown in CategoryKey constructor :
CategoryKey(String name) {
this.name = name;
>hashCache = name.hashCode();
}
This sounds like you try to create a logger with a null category name.
To avoid this, you may use the class to build your loggers :
private static Logger
I'm using Spring BeanExporter to publish log4j configuration
class="org.springframework.jmx.export.MBeanExporter">
class="org.apache.log4j.jmx.HierarchyDynamicMBean"/>
MBeanExporter simpl
Please upload log4j-1.2.12 in apache java-repository
(http://www.apache.org/dist/java-repository/log4j/jars/)
AFAIK it will automatically be synchronized to maven repository on ibiblio.
Nico.
This message contains information that may be privileged or confidential and is
the property of the
Please upload log4j-1.2.12 in apache java-repository
(http://www.apache.org/dist/java-repository/log4j/jars/)
AFAIK it will automatically be synchronized to maven repository on ibiblio.
Nico.
This message contains information that may be privileged or confidential and is
the property of the
I'm so sory my patch is not include in this version ;-(
(http://issues.apache.org/bugzilla/show_bug.cgi?id=35996)
I'll have to wait for 1.2.13...
Nico.
Mark Womack a écrit :
The log4j team is proud to announce the official release of log4j 1.2.12!
This new version contains a number of bug
Just another suggestion : what do you thing about maven way to make ant
script dynamic based on jelly tags ? This could be another way to make
log4j.xml easily extensible.
Nico.
Nicolas De Loof a écrit :
I have no expectation about the version that could include such
enhancement as I
I have no expectation about the version that could include such
enhancement as I've found a workaround using log4j.configuratorClass.
I'd be realy happy to find such functionnality in 1.2.12 or 1.2.13, but
I know it only depends on anyone to provide a patch ! I'll try to have a
look myself.
I
You're right, the ant tag to import properties is a well known and
approved way to customize an existing XML script without having to know
it's internals. Similar functionnality in log4j.xml should be great !
Perhaps an (optional) reuse of ant code could do the job ?
Nico.
Nicolas Martignol
The attribute "props" is declared as package visible and is never set in
DOMConfigurator, and has no setter. AFAIK There is no log4j class that
extends DOMConfigurator, so what is it designed for ?
It is usefull in my app that uses a custom configurator to inject
application properties in th
t your Xml log4j config files. Look for the subtask of the
task.
moran
-----Original Message-
From: Nicolas De Loof [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 02, 2005 11:21 AM
To: log4j-user@logging.apache.org
Subject: home to do variable substitution from another prope
Hello,
I'm using log4j XML configuration format and use system properties for
variable substitution. My current app use lot's of appenders with
various file paths, and I've a requirement to set all this config in a
"simple" configuration file. This means my customer will neither want to
edit
15 matches
Mail list logo