Jacob Kjome wrote:
What I liked about the ServletContext logging was that I could
dynamically create the file using a simple Logger in the Context
element of my context configuration file. This way, all I have to do is
the deploy the app and the log file is created and rolled for me.
I'd like
.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] Behalf Of Andreas Schildbach
Sent: 17 November 2004 15:27
To: [EMAIL PROTECTED]
Subject: Re: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Jacob Kjome wrote:
What I liked about the ServletContext logging
Hi,
There is even one more reason why Tomcat 5.0 logging was better:
With Tomcat 5.0, it was possible to log different web applications to
different log files by using the swallowOutput attribute of the
Context element, even if those applications used the same libraries. I
This is still
Shapira, Yoav wrote:
There is even one more reason why Tomcat 5.0 logging was better:
With Tomcat 5.0, it was possible to log different web applications to
different log files by using the swallowOutput attribute of the
Context element, even if those applications used the same libraries. I
This is
On Wed, 17 Nov 2004 15:37:10 -, Allistair Crossley
[EMAIL PROTECTED] wrote:
Put simply, if you want per-web application logging, you need per-web
application log4j configuration. It's very easy to do but I do understand
that those using System.out will have to spend time refactoring. But
At 01:26 AM 11/13/2004 +0100, you wrote:
On Fri, 12 Nov 2004 12:53:18 -0600, Jonathan Eric Miller
[EMAIL PROTECTED] wrote:
Actually, I guess the default isn't that bad for UNIX/Linux anyway. In
On Windows, I think it's time to start using the .exe wrapper (or
another similar wrapper), rather
by Tomcat 5.5.4.
Cheers, Allistair
-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 11 November 2004 20:34
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hi,
I disagree with this statement, as it's
On Fri, 12 Nov 2004 09:55:20 -, Allistair Crossley
[EMAIL PROTECTED] wrote:
Hi,
I have some new information on this for my case. I created a small JSP that
had a scriplet error and ran it. I am definately using 5.5.4 with Java 5.0.
In this case, I got the error stack trace in stdout.
configuration in
common/classes has just appeared hooray!
Will play around a bit more and let you know how it goes ...
-Original Message-
From: Remy Maucherat [mailto:[EMAIL PROTECTED]
Sent: 12 November 2004 10:07
To: Tomcat Users List
Subject: Re: Tomcat 5.5.4, Logging and the death of my
-
From: Remy Maucherat [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 2:02 PM
Subject: Re: Tomcat 5.5.4, Logging and the death of my friend localhost_log
On Thu, 11 Nov 2004 15:25:48 -, Allistair Crossley
[EMAIL PROTECTED] wrote:
Now, I know
On Fri, 12 Nov 2004 12:53:18 -0600, Jonathan Eric Miller
[EMAIL PROTECTED] wrote:
Actually, I guess the default isn't that bad for UNIX/Linux anyway. In
On Windows, I think it's time to start using the .exe wrapper (or
another similar wrapper), rather than keep using the .bat scripts,
given
Hi Guys,
Bit the bullet and have switched our intranet test server over to JDK 5 /
Tomcat 5.5.4 Stable.
Anyway, I've hit a small hurdle and believe it or not it is not JNDI data
sources .. that stuff worked perfectly!
No, it's the other one .. logging. I am not quite getting where the old
Hi,
I have tried what I believed to be how to do this, e.g I placed a basic
console appender log4j.properties file into tomcat/common/classes and
popped log4j1.2.8 into the common/lib. No logging though.
Where did you attach the console appender? To the root logger or on of
your own packaged?
:[EMAIL PROTECTED]
Sent: 11 November 2004 15:31
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hi,
I have tried what I believed to be how to do this, e.g I
placed a basic
console appender log4j.properties file into tomcat/common/classes
=DEBUG, R
Cheers! A.
-Original Message-
From: Allistair Crossley
Sent: 11 November 2004 15:35
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hey Yoav,
tomcat/common/classes/log4j.properties as follows
log4j.rootLogger=DEBUG
=DEBUG, R
Cheers! A.
-Original Message-
From: Allistair Crossley
Sent: 11 November 2004 15:35
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hey Yoav,
tomcat/common/classes/log4j.properties as follows
log4j.rootLogger=DEBUG, A1
log4j.appender.A1
: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 11 November 2004 15:31
To: Tomcat Users List
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hi,
I have tried what I believed to be how to do this, e.g I
placed a basic
console appender
]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Thursday, November 11, 2004 9:41 AM
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend
localhost_log
Hi again,
I have tried to setup a file appender now without success. When I
On Thu, 11 Nov 2004 15:25:48 -, Allistair Crossley
[EMAIL PROTECTED] wrote:
Now, I know Logger has been removed from 5.5 series and that we are supposed
to be using some kind of log4j / commons-logging stylee way but am fairly
surprised that 5.5.4 did not come with a basic setup for this.
Subject: RE: Tomcat 5.5.4, Logging and the death of my friend localhost_log
this is very true actually, i.e the old JSP stack trace errors and so on
will not be directed into log4j-type logs .. that's not good at all i
agree. And I know there is an exception occurring right now, but it's
Hi,
BTW, does anyone know if there are any advantages to using Log4J over
Java
Numerous: http://logging.apache.org/log4j/docs/documentation.html has
several articles. If you're looking for anything but the simplest
logging features, log4j is far superior.
Yoav
This e-mail, including any
On Thu, 11 Nov 2004 15:09:08 -0500, Shapira, Yoav [EMAIL PROTECTED] wrote:
If you're looking for anything but the simplest
logging features, log4j is far superior.
I disagree with this statement, as it's too general. Personally, I
consider what is definitely superior in log4j are the many
Hi,
I disagree with this statement, as it's too general. Personally, I
consider what is definitely superior in log4j are the many logger
implementations. As far as I can tell, these could (= should) be
ported to the java.logging API.
Sun can port those any time it wants -- they have the
On Thu, 11 Nov 2004 15:34:09 -0500, Shapira, Yoav [EMAIL PROTECTED] wrote:
Many of the relevant logging standards (given that there's no JSR) are
derived (if not plain copied) from log4j. Furthermore, the log4j people
have been working for improve standards and teamwork in this area, with
24 matches
Mail list logo
