Migration to logging.apache.org
Hello, This is just to inform you that subsequent to the creation of the Apache Logging Services project, the existing log4j-dev and log4j-user lists will be migrating to logging.apache.org from jakarta.apache.org. The migration should be seamless in the sense that current subscribers will automatically be subscribers of the new lists. The migration is expected to occur this weekend or early next week. -- Ceki Gülcü For log4j documentation consider The complete log4j manual ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
FileWatchdog - file delete
Hi I've been using the FileWatchdog class to check changes in a file. but it seems the method doOnChange() is not invoked when the file is deleted. Why ? Phillip Grobler - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: FileWatchdog - file delete
Seems I've been mistaken it only happens if you watch a empty file of size 0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Shutting down specific instance of log file
Hi everyone.
I'm currently facing a problem where I have two instances of log files, one
running internally using Turbine, and the other for a process withing my
application which runs for about an hour every day. For this separate
process I have my own log file, and I wish to shut it down after it is
finished. The properties file for that log file looks like this:
log4j.rootLogger=DEBUG, default
log4j.appender.default=org.apache.log4j.RollingFileAppender
log4j.appender.default.layout=org.apache.log4j.PatternLayout
log4j.appender.default.File=${file.name}.log
log4j.appender.default.datePattern='.'-MM-dd
log4j.appender.default.layout.ConversionPattern=[%d] [%t] %-5p %M.%L - %m%n
The problem is in my code, the only way I have found to terminate this log
file is by calling LogManager.shutdown(); which unfortunately closses all
log files down (including the Turbine log file) which is not the intended
purpose. Can anyone offer any suggestions for shutting down only one
specific log file??
Thanks,
Damian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
WIN2K and Linux, not same behavior on Rolling File Appender in Servlets
I had a demo this week using a WAR file that i deployed many times on
Windows with great results. This week using the same WAR file on Linux for
the first time, EVERY LOGGER Call threw an exception $%^# not my best
week for demos.
some hypothesis follows and i would greatly appreciate expert guidance on
this...
Note that jar log4j-1.2.8.jar contains PropertyConfigurator.class and that
this jar is in the following 2 WebApp directories under Tomcat/BASE...
NOTE ALSO that NONE of the Tomcat Common, shared, endorsed libs contain
log4j-1.2.8.jar.
#1
[EMAIL PROTECTED] /cygdrive/g/jakarta-tomcat-5.0.16
$ find -name log4j-1.2.8.jar
./webapps/axis/WEB-INF/lib/log4j-1.2.8.jar
./webapps/ftp-examples/WEB-INF/lib/log4j-1.2.8.jar
-
static code for log4j configuration that i use in every class...
#2
static
{
log = Logger.getLogger((this.class).getName());
PropertyConfigurator.configure(
this.class.getClassLoader()
.getResource(
config/log4j.properties
)
);
}
- log4j.properties file (elided) -
#3
# LOGFILE is set to be a File appender using a PatternLayout.
#log4j.appender.LOGFILE=org.apache.log4j.FileAppender
log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.File=logs/ftp.log-- linux exception on this
-- File does NOT EXIST
- Behavior of War deployed on Windows...
NOTE that the code at #2 operates in a Web app. and will load
PropertyConfigurator class from the jar located at that webapp's context (
webapps/this.context/WEB-INF/lib/log4j-1.2.8.jar ).
However, in Windows, the crazy feature is that the fileAppender from #3 gets
written NOT at the Webapp's context , but a Tomcat's BASE as in
G:\jakarta-tomcat-5.0.16\logs. This seem's impossible to me??
--- Behavior of War deployed on Linux...
every log.debug() call throws a file does not exist ( logs/ftp.log )
exception. Why is this? Like on Windows example above, here the Linux path
jakarta-tomcat-5.0.16/logs exists but the system never writes the appender
there.
Its as if on Linux, the only place it will try to write the appender is to:
webapps/this.context/logs/ftp.log and since there is no logs directory
under each
web context, the error is thrown...
Since the WAR file does not define a path under every WEBAPP that includes
this.context/logs , all the logger calls throw exceptions...
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
