log4j.appender.CHAINSAW_AXIS2.Port=4452
log4j.appender.CHAINSAW_AXIS2.LocationInfo=true
# ---
#- Set your loggers priority to what you need ---
# Logger logging WHAT it logs WHO is actually logging
log4j.logger.org.apache.catalina=INFO, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.coyote=INFO,CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.jasper=INFO,CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.jk=INFO,CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.tomcat=INFO,CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.commons=INFO, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.axiom=WARN, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.axis2=INFO, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.org.apache.axis2.deployment=DEBUG, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.de.hunsicker.jalopy.io=FATAL, CONSOLE, R, CHAINSAW_CLIENT
log4j.logger.httpclient.wire.header=FATAL, CONSOLE, R, CHAINSAW_CLIENT
# ---
#- create the SpServer Logger ---
# this is the CONFIGURED logger for the SpServer.java JavaPart
# the Configurator strips of the logger_prefix log4j.logger.
# the logger is then known in the hierarchy as
# axawl.spezpla.servers.SpezplaService.SpServer
#retrive this configured logger from log4j.hierarchy through
# Logger log = Logger.getLogger(SpServer.class);
log4j.logger.axawl.spezpla.servers.SpezplaService.SpServer=INFO, LOGFILE,
CHAINSAW_AXIS2
# ---
# define the additivities used to prevent logging twice the same msg
# NOTE: each logger needs an additivity set or you risk logging twice
#
log4j.additivity.org.apache.axiom=false
log4j.additivity.org.apache.axis2=false
log4j.additivity.org.apache.axis2.deployment=false
log4j.additivity.org.apache.catalina=false
log4j.additivity.org.apache.coyote=false
log4j.additivity.org.apache.jasper=false
log4j.additivity.org.apache.jk=false
log4j.additivity.org.apache.commons=false
# to prevent that logging events are propagated to parent loggers
# and finally arrive at the root loggers appender, printed to the root-
# loggers files i.e. additivity must be set to false to prevent this.
# please goto http://logging.apache.org/log4j/1.2/manual.html and read
# the short manual or buy the full manual
log4j.additivity.axawl.spezpla.servers.SpezplaService.SpServer=false
IA64-2
Josef
-Ursprüngliche Nachricht-
Von: Jacob Kjome [mailto:h...@visi.com]
Gesendet: Sonntag, 4. September 2011 20:16
An: Log4J Users List
Betreff: Re: Changing Level of Logging during runtime
There used to be a nice open source, Struts-based, Log4j configuration app out
there, but it seems to have disappeared. There's a simple one in the
Log4j-sandbox you can try...
http://svn.apache.org/repos/asf/logging/sandbox/log4j/log4j_sandbox/tags/LOG4J_SANDBOX_ALPHA3/src/java/org/apache/log4j/servlet/ConfigurationServlet.java
Note that I specifically point to the tag LOG4J_SANDBOX_ALPHA3 because later
tags were based on the now defunct Log4j-1.3 codebase and the trunk, I believe,
continues to be based on the said defunct codebase.
Jake
On 9/2/2011 2:58 AM, Amitabh78 wrote:
Hi, I want to change the level og logging during runtime. The change in level
should be in immediate effect i.e. when admin changes the level og logging
from Debug to Info through UI Screen, the logging at debug level should be
stopped immediately.
-
To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-user-h...@logging.apache.org
