I'm *guessing* you're facing some of the issues I have been.
I believe you'll essentially need to set up a separate LoggerRepository
(based on classloader, not thread or contextual class loader) and
provide separate config files for each.
I've got log4j.jar in my WEB-INF/lib, I'm using my own
s
On Fri, 2005-03-18 at 11:25 +0530, Joy Kenneth Harry wrote:
> Hi,
> I have a webapp in tomcat. I am using a separate Log4j.xml for it, in
> its WEB-INF classes folder.
>
> I've also put a Log4j.xml in TOMCAT_HOME/ common/classes and set it to
> false so that I do not get the general Tomcat logs.
>
What you want to use is the Logger instance that is defined for
this context via your server.xml
From a servlet,
getServletContext().log("theMessage");
Thanks go to Yoav Shapira
Millennium ChemInformatics
The catalina_log file is the Logger element under the "Catalina"
elemen
Thanks for the good info!
--Original Message--
From: "Mark Mynsted" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
Sent: March 23, 2001 3:07:21 PM GMT
Subject: Re: Logging in tomcat
I think the simplest way is to just use
application.
Thanks for the info! That helps. I'll check out the log4j.
--Original Message--
From: Anuj Agrawal <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: March 23, 2001 12:11:51 AM GMT
Subject: Re: Logging in tomcat
tomcat user wrote:
> I haven't found much info on lo
I think the simplest way is to just use
application.log("This is a message to be logged");
This goes to the Servlet.log. A little better maybe would be to define something like:
String logHeader = request.getServletPath() + ": ";
Then use
application.log(logHeader + "This is a message to be log
Yes, setting the verbosity level is one way to up the amount of log
information you are getting. Be aware, if you turn it way up (so you log
quite a lot), the consequences can be performance impacting (and not in a
good way).
There are good reasons the default levels are set to log less informat
