hihi Paul,
i tried your suggestion but it still did not work. however, i finally
found out why.
the problem web application had the following code:
try {
System.setProperty(org.apache.commons.logging.Log,
org.apache.commons.logging.impl.Log4JCategoryLog);
both Tomcat and your web apps will use separate log4j
configurations.
Thanks,
Seva
From: Paul Austin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 31, 2005 1:30 PM
To: Tomcat Users List
Subject: Re: Tomcat 5.5 classloader log4j vs JCL issue
-
From: Woodchuck [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 06, 2005 11:10 AM
To: Tomcat Users List; Seva Popov
Subject: RE: Tomcat 5.5 classloader log4j vs JCL issue
hihi Seva,
yes, your suggestion also works. i tried it to confirm, and it was my
backup plan to do in case i couldn't
I'm having the same issue and after trying to follow the instructions given by
Paul Austin, I've got stuck on the part that says to add a listener.
There's no place for a listener in web.xml according to the dtd validation
file. Am I wrong ? (I'm using Tomcat 5.5.9 with the struts framework)
Luc,
The listener element is only valid in the Servlet 2.3 web.xml file, if
using a previous servlet version use the attached servlet set to load at
startup before any of the other servlets.
The jar containing my classes should be included in your WEB-INF/lib
directory in each web application.
hihi all,
on my TC 5.5.9 installation i deployed several web applications that
uses the default JCL logging. that is, i placed a simple
logging.properties file into each web app's WEB-INF/classes folder and
i have per web app logging. everything works beautifully.
then i installed a new web
Woodchuck,
The following web page describes this situation and a solution to the problem.
http://www.qos.ch/logging/sc.jsp
I have attached the solution that I created this week based on the information above. To compile you will need servlet-api.jar and log4j.jar to compile.
Include the jar
From: Woodchuck [EMAIL PROTECTED]
then i installed a new web app that forced me to place
commons-logging.jar and log4j.jar into the ${Tomcat}/common/lib folder.
as a result, all my previous per web app logging no longer works.
does anyone have any suggestions on how i can have per web app
hihi Paul,
thanks so much for your help! i will definitely give this a try and
post my results.
woodchuck
--- Paul Austin [EMAIL PROTECTED] wrote:
Woodchuck,
The following web page describes this situation and a solution to the
problem.
http://www.qos.ch/logging/sc.jsp
I have
Subject: Re: Tomcat 5.5 classloader log4j vs JCL issue
Woodchuck,
The following web page describes this situation and a solution to the
problem.
http://www.qos.ch/logging/sc.jsp
I have attached the solution that I created this week based on the
information above. To compile you will need servlet
hihi Wendy,
hehe. that also crossed my mind, i wish that was an option, but i
can't unfortunately.:)
woodchuck
--- Wendy Smoak [EMAIL PROTECTED] wrote:
Is giving the uncooperative webapp its own Tomcat instance an option?
That's what I'd do. I have a third-party app that insists on
11 matches
Mail list logo
