Here is a much more verbose explanation of logging from personal experience. I work as
a consultant, so most of the time there are established administration procedures for
generating nightly reports and for cleaning up old logs.
Important issues related to logs are:
1. should all logs go in
Don't count on being able to write to anywhere within your webapp. Tomcat,
by default, expands your webapp to a directory and deploys your app from
there. This gives you access to within your webapp via File IO. However,
this is not guaranteed by the servlet spec. Your app can be run
Howdy,
Listen to Jacob -- I wish more people did what he recommended in his
post. Also use log4j. ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 19, 2003 2:30 PM
To: Tomcat Users List
Subject:
here are some other considerations. For some of the
projects I've worked on in the past, there were
established directories for logs. Therefore I used
log4j to write my logs asynchronisly.
logging isn't as simple as write stuff to file. You
have to take into consideration other things like how
, February 19, 2003 8:19 AM
To: Tomcat Users List
Subject: RE: Best Logging practices
Howdy,
Listen to Jacob -- I wish more people did what he recommended in his
post. Also use log4j. ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL
AM
To: Tomcat Users List
Subject: RE: Best Logging practices
Howdy,
Listen to Jacob -- I wish more people did what he
recommended in his
post. Also use log4j. ;)
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Manavendra Gupta [mailto:[EMAIL PROTECTED
or the JDK1.4 logger.
Regards
Jim.
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]]
Sent: 19 February 2003 15:07
To: Tomcat Users List
Subject: RE: Best Logging practices
the latest version of log4j already supports the new
logging API. The implementation
Users List'
Subject: RE: Best Logging practices
I would not recommend using commons-logging in a web-app. If you want to
separately configure the logging requirements of an application you have
to
deploy it with its own logging properties file (log4j.properties for
log4j).
For commons-logging to pick
I just noticed the typos in my post. what I meant to
say is, use log4j since commons-logging uses it.
using commons-logging will require more work than
using log4j directly. there are numerous examples
distributed with log4j, including how to extend it
with custom logging categories. sorry for
Howdy,
What do you think of this opinion: I am inclined to use the JDK1.4
logger just because it's included in rt.jar, thus fewer jars and
shorter
classpath, and all that.
I think everyone is free to have their own opinion.
I don't think the length of the classpath is a relevant argument to
I know what you mean, but maybe he doesn't really need what log4j
offers in better ways than jdk1.4
I use it for very simple logging and have no problems with it.
On Wed, 2003-02-19 at 12:57, Shapira, Yoav wrote:
Howdy,
What do you think of this opinion: I am inclined to use the JDK1.4
in
Tomcat.
Regards
Jim.
-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED]]
Sent: 19 February 2003 15:52
To: Tomcat Users List
Subject: RE: Best Logging practices
I just noticed the typos in my post. what I meant to
say is, use log4j since commons-logging uses
Howdy,
I know what you mean, but maybe he doesn't really need what log4j
offers in better ways than jdk1.4
I use it for very simple logging and have no problems with it.
You could be right. If his use case is very simple and will never grow
more complex.
One thing to keep in mind though,
From: Arachtingi, Mike [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 7:48 AM
Subject: RE: Best Logging practices
What do you think of this opinion: I am inclined to use the JDK1.4
logger just because it's included in rt.jar, thus fewer jars and shorter
classpath, and all
On Wed, Feb 19, 2003 at 08:15:20AM -0600, Jacob Kjome wrote:
Don't count on being able to write to anywhere within your webapp. Tomcat,
by default, expands your webapp to a directory and deploys your app from
there. This gives you access to within your webapp via File IO. However,
this
From: Steven J. Owens [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 1:27 PM
Subject: Re: Best Logging practices
This is something that's bugged me for quite a while (in fact,
since jars were introduced :-). There's no way, as far as I'm aware,
to elegantly handle configurable
On Wed, Feb 19, 2003 at 02:43:50PM -0800, Will Hartung wrote:
One thought though; for web applications you're supposed to get
external resources by configuring them in the web.xml and using
ServletContext.getResourceAsStream(). This only supports input
streams, but I've always sort
At 02:43 PM 2/19/2003, you wrote:
One thought though; for web applications you're supposed to get
external resources by configuring them in the web.xml and using
ServletContext.getResourceAsStream(). This only supports input
streams, but I've always sort of felt it should support output
From: Justin Ruthenbeck [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 3:15 PM
Subject: Re: Best Logging practices
I'm sure this is a contentious topic ripe for disagreement, but I see no
reason why a .war file should be read-only. The point of packaging your
application
Without an intent to offend anyone, I'd say majority of the posts were
centered around what tools to use, rather than the best practices itself
(apart from the posts of Jacob and Peter Lin).
So, from what I understand:
1. Web applications written using tomcat should have the logging path
Your question is now becoming a lot more logging-in-general oriented where
it was about logging from webapps before. I suggest you look to the
experts on the log4j-user list or, better yet, buy the book on using log4j:
http://www.qos.ch/shop/products/clm_t.jsp
This is loaded with information
[EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 8:51 PM
Subject: Re: Best Logging practices
Your question is now becoming a lot more logging-in-general oriented where
it was about logging from webapps before. I suggest you look to the
experts on the log4j-user list or, better yet, buy
Hi Peter,
Thanks a lot for the response.
here are some other considerations. For some of the
projects I've worked on in the past, there were
established directories for logs. Therefore I used
log4j to write my logs asynchronisly.
Could you elaborate on established directories? I assume these
themselves.
Regards,
Manav.
- Original Message -
From: Jacob Kjome [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Wednesday, February 19, 2003 8:51 PM
Subject: Re: Best Logging practices
Your question is now becoming a lot more logging-in-general oriented where
24 matches
Mail list logo
