Keith
-Original Message-
From: Keith Bottner [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 08, 2004 1:08 PM
To: [EMAIL PROTECTED]
Subject: Log4j.properties not read for included jar
I am using Tomcat to publish a web application. I use log4j throughout my
application and configure it wit
bugEnabled())
logger.log(Level.DEBUG, output);
}
...
}
Any additional ideas? Anyone???
Keith
-Original Message-
From: Yoav Shapira [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 08, 2004 1:25 PM
To: Log4J Users List
Subject: Re: Log4j.properties not read for includ
Hi,
You can try setting the logger for the deli root package at DEBUG level, and/or
adding a special appender for it.
You don't need a separate log4j configuration file for it: one per classloader
repository is enough. deli.jar is in WEB-INF/lib under the same webapp where
your WEB-INF/classes th
I am using Tomcat to publish a web application. I use log4j throughout my
application and configure it with the following log4j.properties file.
# Create a single console appender that logs INFO and higher
log4j.rootLogger=WARN, stdout log4j.com.blt=DEBUG, stdout
com.hp.hpl.deli.Workspace=DEBUG, s
> Is there a way to force the use of a certain
> properties file ?
Yes, you could use the code I sent to the list... Give your properties file
another name than log4j.properties (e.g. log4j.appname.properties) and call
the method with that name.
Christian
--
+++ GMX - die erste Adresse für Mail
mman
> d. Much simpler ;)
>
> Yoav Shapira
> Millennium ChemInformatics
>
>
> >-Original Message-
> >From: Christian Hufgard [mailto:[EMAIL PROTECTED]
> >Sent: Tuesday, January 27, 2004 5:57 AM
> >To: Log4J Users List
> >Subject: Re: log4
get the logging working.
Though not directly applicable, I hope this may be of some assistance.
Regards
Joe
-Original Message-
From: Ionel GARDAIS [mailto:[EMAIL PROTECTED]
Sent: 27 January 2004 14:06
To: Log4J Users List
Subject: RE: log4j.properties not read
Hi there,
As I told, that
Hi there,
As I told, that what i've done.
And I saw that the log4j.properties file used was not
mine.
Even by adding my file at the beginning of the
classpath, it does not use it.
I tried to add -Dlog4j.properties and
-Dlog4j.properties.file but none worked.
Is there a way to force the use of a
Christian,
I used -dlog4j.debug=true in my command line and I saw
that log4j is using another log4j.properties file
(from a third-party jar file)
Again, the first entry in my classpath is my own
log4j.porperties file.
Also I still have the
-Dlog4j.properties= in the command
line.
Why don't it g
>Subject: Re: log4j.properties not read
>
>Hi Ionel,
>
>you could use the following work-around to determine, what your log4j is
>doing - it did help me too :)
>
>public void initializeLog4j(String propertyfileName) {
> System.out.println("looking for property file
Hi Ionel,
you could use the following work-around to determine, what your log4j is
doing - it did help me too :)
public void initializeLog4j(String propertyfileName) {
System.out.println("looking for property file with name "+
propertyfileName);
url =
this.getClass().getClassLoader().
Hi,
I am running an application that uses log4j.
I add the nedded log4j jars and the log4j.properties
file on its classpath.
Unfortunatly, I see none of the declared log files on
my folders.
I tries to add a
-Dlog4j.properties= but it
does not help : i am still missing the log files.
How to for
12 matches
Mail list logo
