-Original Message-
From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED]
Sent: 22 August 2007 21:19
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> There wasn't any trace at all - I added my own logging to tell me that
> one s
Upgrade to Tomcat 6
Ashley Hollands wrote:
> There wasn't any trace at all - I added my own logging to tell me that
> one server had sent the message, but on the other server there was no
> sign of why it wasn't being delivered to the ChannelListener until I
> turned on d
ist
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> OK - I'll run through the steps from scratch again and see if I have
> more joy this time.
>
let me know how it goes, I can help out more.
> By the way, I have been using Tribes in my application an
Sent: 22 August 2007 20:21
To: Tomcat Users List
Subject: Re: Logging Problem on Upgrade to Tomcat 6
Ashley Hollands wrote:
> 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 ap
,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
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
>
>
>&
s
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 t
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 anybo
