What is confusing me is that I never had to catch the exception and
log it from within my application in Tomcat 4, 5 or 5.5 - it just appeared
in the web app log automatically.

Is there no way to configure Log4J/Tomcat 6 to do the same thing without
having to do as you suggest?

Ashley

-----Original Message-----
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] 
Sent: 22 August 2007 19:51
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6

it will only log to the webapp.log if your application catches the
exception, then issues a log.error("msg",exception) (tomcat will do the same
assuming it was correctly configured)

if you provide a sample war, I can validate it for you

Filip

Ashley Hollands wrote:
> I did build the extra JAR files as described in the documentation.
>
> Whether I am using Log4J at the Tomcat level, or using Tomcat's 
> default logging, I do get log messages in my web app log. For example 
> if I add the following to my web app log4j.properties:
>
> log4j.logger.com.mycompany=INFO
>
> it logs these messages to the web app log no problem - both with Log4J 
> and Tomcat's default logging at the top-level.
>
> My problem is that it isn't logging Exceptions even though as I 
> understand it, it should be logging anything with priority ERROR or 
> higher (lower?) that is generated by the web app to the web app log.
>
> Ashley
>
> -----Original Message-----
> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
> Sent: 22 August 2007 19:12
> To: Tomcat Users List
> Subject: Re: Logging Problem on Upgrade to Tomcat 6
>
> Ashley Hollands wrote:
>   
>> Thanks for the reply Filip
>>
>>   
>>     
>>> if you want a global log4j (instead of tomcat's own framework)...
>>>     
>>>       
>> I have configured Tomcat to use Log4J at the top-level using the 
>> documentation you recommend no problem, but it doesn't solve my 
>> problem.
>>
>> What I want is for the Exception to get logged at the web application 
>> level (I'm not bothered whether it also gets logged at the Tomcat 
>> level or not - Using Tomcat 5.5, it used to get logged at the web 
>> application level and not at the Tomcat level at all).
>>   
>>     
> you want it to go to webapp.log, as you configured below?
> and you did build the additional JARs that Tomcat uses and removed the 
> usage of Tomcat's own logging.
> from your explanation, it doesn't sound like you took these steps, 
> cause if you did, tomcat would log into your log4j, and not its own 
> mechanism
>
> Filip
>   
>> Ashley
>>
>> -----Original Message-----
>> From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
>> Sent: 22 August 2007 18:03
>> To: Tomcat Users List
>> Subject: Re: Logging Problem on Upgrade to Tomcat 6
>>
>> if you want a global log4j (instead of tomcat's own framework) 
>> http://tomcat.apache.org/tomcat-6.0-doc/logging.html
>> then you will need to be tomcat-juli.jar and tomcat-juli-adapters.jar 
>> as described in the docs,
>>
>> let me know if you need more clarification Filip
>>
>> Ashley Hollands wrote:
>>   
>>     
>>> Hi
>>>
>>> I have recently upgraded from Tomcat 5.5 to 6.0 and from Java 1.5 to 
>>> 6.
>>>
>>> I use Log4J for all my web application logging and have discovered 
>>> that after the upgrade, any exceptions thrown in the web application 
>>> are not logged to my web application log, but to the top-level 
>>> Tomcat log.
>>>
>>> Does anybody know how I can make sure any java.lang.Exceptions 
>>> thrown are logged to the web application log? It used to work fine 
>>> with the previous versions of Tomcat (4, 5 and 5.5).
>>>
>>> My web application log4j.properties file is as follows if that helps:
>>>
>>> log4j.rootCategory=ERROR, logfile
>>>
>>> log4j.appender.logfile=org.apache.log4j.DailyRollingFileAppender
>>> log4j.appender.logfile.DatePattern='.'yyyy-MM-dd
>>> log4j.appender.logfile.File=/logs/tomcat/webapp.log
>>> log4j.appender.logfile.layout=org.apache.log4j.PatternLayout
>>> log4j.appender.logfile.layout.ConversionPattern=%d %p [%c] - %m%n
>>>
>>> Thanks
>>>
>>> Ashley
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> - To start a new topic, e-mail: users@tomcat.apache.org To 
>>> unsubscribe,
>>> e-mail: [EMAIL PROTECTED]
>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>
>>>
>>>
>>>   
>>>     
>>>       
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
>> e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>> ---------------------------------------------------------------------
>> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
>> e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>   
>>     
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
> e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, 
> e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>   


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe,
e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to