e log4j by setting a system property. See c-l
documentation for more details.
Conclusions:
The "discovery process" of commons-logging is not only weak. it is a major
bug
and annoyance! I had problems with it without ever using the logging itself,
who would expect that?
The java classloader
erent, as they are loaded by different classloaders.
Conclusions:
The "discovery process" of commons-logging is not only weak. it is a major bug
and annoyance! I had problems with it without ever using the logging itself,
who would expect that?
The java classloader architecture is ro
server and hence don't
want to suggest something wrong.
Swami
> -Original Message-
> From: Kiefer, Hardy [mailto:[EMAIL PROTECTED]]
> Sent: August 19, 2002 9:12 AM
> To: 'Log4J Users List'
> Subject: RE: classloader problem
>
>
> Now we could read
Now we could read the property file with the J2EE classloader with
void configureLog4j( String log4JConfigFile ) {
try {
InputStream is =
getClass().getResourceAsStream(log4JConfigFile);
Properties theProperties = new Properties
ClassLoader.getSystemResource().
log4j: Could not find resource: [C: ..our path..
\lib\classes\log4j.properties].
log4j:ERROR No appenders could be found for category (.).
log4j:ERROR Please initialize the log4j system properly.
I think the classloader of J2EE on Windows cannot load the property file.
But what can we
Kiefer, Hardy [mailto:[EMAIL PROTECTED]]
> Sent: August 15, 2002 3:09 AM
> To: 'Log4J Users List'
> Cc: Buettner, Waltraud
> Subject: RE: classloader problem
>
>
> Swami,
>
> We gave only the file name without the path, but the file is
> located in a
> dir
Swami,
We gave only the file name without the path, but the file is located in a
directory which is in the Java CLASSPATH.
Hardy
-Original Message-
From: Swami Iyer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 7:31 PM
To: 'Log4J Users List'
Subject: RE: c
r, Waltraud
> Subject: RE: classloader problem
>
>
> Bhushan,
>
> We tried both but without success.
>
> Hardy
>
> -Original Message-
> From: Bhangale, Bhushan [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 14, 2002 5:59 PM
> To: 'Log4J Users
Bhushan,
We tried both but without success.
Hardy
-Original Message-
From: Bhangale, Bhushan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 5:59 PM
To: 'Log4J Users List'
Subject: RE: classloader problem
Then it is fine. It should work.
Is your log4j configur
PROTECTED]]
Sent: Wednesday, August 14, 2002 11:36 AM
To: 'Log4J Users List'
Cc: Buettner, Waltraud
Subject: RE: classloader problem
Hi Bhushan,
Thanks for your mail,
but we start our component in a cmd file on windows with
java -cp %J2EE_CLASSPATH% ...
So the J2EE_CLASSPATH should
: Wednesday, August 14, 2002 4:22 PM
To: 'Log4J Users List'
Subject: RE: classloader problem
You are adding the log4j.properties path in J2EE_CLASSPATH System variable
whereas you need to add it in CLASSPATH system variable which is a standard
one.
All the properties file reader in java looks f
using.
-Original Message-
From: Kiefer, Hardy [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 14, 2002 5:36 AM
To: '[EMAIL PROTECTED]'
Subject: classloader problem
> Hello All,
> can anybody help me.
> I use the application server included in j2eesdk1.3.1 and my comp
> Hello All,
> can anybody help me.
> I use the application server included in j2eesdk1.3.1 and my component
> uses
> log4j 1.1.3. The problem is, that log4j.properties can never be loaded,
> but it is in the J2EE_CLASSPATH.
>
> With -Dlog4j.ConfigDebug=true I got:
>
> log4j: Trying to find [lo
s loader and others are being loaded by the
>context class loader, which is the default JRE loader.
My mistake. I should not write emails past midnight. What I meant was
log4j does not have its own classloader. I'll change the
PropertyConfigurator. Thanks for the valuable information. Ce
> This FAQ item is actually misleading.
>
> Log4j does not attempt to do any class loading itself. I
> repeat, log4j does not
> do classloading.
Actually, it's when the PropertyConfigurator loads an appender class that it
calls Thread.currentThread().getContextClassLoader().loadClass(name). The
ot
do classloading.
At 16:35 18.01.2002 -0700, you wrote:
>Hello,
>
>I am using log4j 1.2alpha6, and have run into a problem with the new
>ClassLoader behavior. I am running some JUnit tests through Ant 1.4.1, and
>when log4j tries to load my appender class named in the properties
Hello,
I am using log4j 1.2alpha6, and have run into a problem with the new
ClassLoader behavior. I am running some JUnit tests through Ant 1.4.1, and
when log4j tries to load my appender class named in the properties file, it
fails with this error:
log4j:ERROR: A "foo.mumble.MyApp
17 matches
Mail list logo
