Hello Ceki,
I got my problem solved. I deleted all the other
log4j.xml files from my pc, may be from cache the
application server is taking some other log4j files.
This solved my problem.
Thanks for all your help and guidence.
thanks and regards
--- Ceki Gülcü [EMAIL PROTECTED] wrote:
Can
Can you provide the exception? Also, does using log4j 1.2.8 change
anything? Your problem might also be related to
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17323
At 10:29 AM 2/26/2003 -0800, you wrote:
Hello All,
I am facing the following problem. I am using a
log4j.xml file for
-
From: Charles N. Harvey III [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 31, 2002 10:01 AM
To: Tomcat Users List
Subject: RE: log4j in tomcat
I think I know what the problem is. To add log4j to Tomcat you added an
extra parameter to either startup.bat or catalina.bat right? (I can't
Howdy,
I don't know the answer, but I wanted to say I'm very interested in this question as
well. Mr. Gülcü or anyone else care to comment? ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Jacob Kjome [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 30, 2002 8:52 AM
The reason that it should be in WEB-INF/lib not int TOMCAT_HOME/lib is
that log4j used to have problems loading the config file if you used the
server library path.
This is because the server classloader cannot see anything in the
application classloader.
If you are using a single
Jake,
Very good question.
Log4j 1.2 introduced the concept of RepositorySelectors specifically
to deal with this problem. Unless the container does for you (which
Tomcat does not) you'd have to write your own RepositorySelector.
Writing a selector is trivial if you control the application
Ceki,
Wouldn't this be another good example of a case where allowing your own
repository selector is a good idea?
I discussed this before:
http://marc.theaimsgroup.com/?t=10148577083r=1w=2
I suggest that until 1.3 is released (which *should* deal with this
problem by having separate
