No, I think this is a problem that will bite other develoeprs so it's
really helpful to report the problem as you have done. Can you explain
where the properties files were located because I don't really get it.
By the way, the "Dunce" cap is a resource shared by most developers causing
much c
Never mind.
The problem I was having was that, unbeknownst to me, the app's EJBs
were hitting their own log4j properties file, which had very different
settings from the file I was using.
For some reason, bouncing the server resulted in MY properties file
getting used, while a re-deploy was picki
> Anyway, make sure that you have one, i.e. 1, log4j-x.jar lying around.
Done. No luck.
I've obsessively gone through my machine, made sure there's only one
log4j*.jar file lying around, made sure that no log4j*.jar files are
getting wrapped into any of the .ear or .war files I'm deploying. I'v
-- Pete
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 27, 2002 12:45 PM
To: Log4J Users List
Subject: Re[2]: Problem with Log4j and Weblogic hot deploy
Hello Pete,
I think you missed the meaning of what was asked. What was meant by
the quest
45 PM
To: Log4J Users List
Subject: Re[2]: Problem with Log4j and Weblogic hot deploy
Hello Pete,
I think you missed the meaning of what was asked. What was meant by
the question was "Do you have log4j-x.jar in a number of places?" was
"Do you have multiple instances of log4j.jar
Hello Pete,
I think you missed the meaning of what was asked. What was meant by
the question was "Do you have log4j-x.jar in a number of places?" was
"Do you have multiple instances of log4j.jar in your Weblogic
install"? So, do you have, maybe one log4j.jar (forget versions for
now) in the clas
> Do you have log4j-x.jar in a number of places?
Yes, but that's true of a lot of other .jar files as well, and they're
working fine.
> Have you checked the WL 7 database?
I haven't been able to find any kind of WL database on the BEA site;
even their "dev2dev" section is a touch heavy on marke
I am not aware of this problem. Since WL 7.0 uses log4j in some of its own
components, I am guessing a class loader problem. Do you have log4j-x.jar
in a number of places? Have you checked the WL 7 database?
At 15:42 26.11.2002 -0500, you wrote:
Hello.
I'm having a problem with log4j that is
Hello.
I'm having a problem with log4j that is absolutely baffling me. If
anybody has so much as a theory for what I'm seeing, I'd love to hear
it.
I'm developing a web app running under BEA Weblogic 7.0, and I'm trying
to set up log4j as my logging mechanism. When I initially start the
server,
