If you deploy more than one
webapp, log4j doesn't attempt to self-configure in the second or any
subsequent webapps.
Just to close out this thread - no big surprise here - I found the bug
in a library that I was deploying in one of my webapps that caused
this behaviour.
Some code was
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 4/6/2009 5:42 PM, Dan Armbrust wrote:
System.setProperty(log4j.defaultInitOverride, true);
And also, since this is a global JVM variable, one webapp setting this
property would affect the behaviour of other webapps - but again, it
would
On Thu, Apr 2, 2009 at 9:55 PM, Caldarale, Charles R
chuck.caldar...@unisys.com wrote:
From: Dan Armbrust [mailto:daniel.armbrust.l...@gmail.com]
Subject: And even further into the black magic of logging configuration
within tomcat...
So, why didn't log4j try to find the log4j.properties
So, after my long thread to figure out the missing stack traces from a
bad listener configuration, I _thought_ I knew what I needed to
correct.
It seemed that Tomcat was trying to use log4j shipped with my webapp,
before my webapp had configured log4j.
Supplying a log4.properties file in the
From: Dan Armbrust [mailto:daniel.armbrust.l...@gmail.com]
Subject: And even further into the black magic of logging configuration
within tomcat...
So, why didn't log4j try to find the log4j.properties
file for the second webapp?
Verify that you have separate log4j.properties files
:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Tuesday, January 13, 2009, 1:13 PM
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
Ok. What I am asking
wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Tuesday, January 13, 2009, 1:13 PM
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
Ok. What I am
--- On Tue, 1/13/09, Caldarale, Charles R chuck.caldar...@unisys.com wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Tuesday, January 13, 2009, 11:29 AM
From: Jay [mailto:difficult
...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Monday, January 12, 2009, 6:41 PM
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
There are many web apps. Log4j logger is used in all web apps
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
I guess, Tomcat is directing all the log4j log messages
in the code to system.out which in turn is being written
to catalina.out
You laboring under a misconception - Tomcat doesn't interact with log4j
--- On Mon, 1/12/09, Caldarale, Charles R chuck.caldar...@unisys.com wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Monday, January 12, 2009, 6:41 PM
From: Jay [mailto:difficult
Ok. What I am asking is, is there a mechanism to roll catalina.out based on
size of the file.
Thanks
--- On Tue, 1/13/09, Caldarale, Charles R chuck.caldar...@unisys.com wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
Ok. What I am asking is, is there a mechanism to roll
catalina.out based on size of the file.
You're missing the point. If you configure log4j properly AND your webapps do
not make direct use
, Caldarale, Charles R chuck.caldar...@unisys.com wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date: Sunday, January 11, 2009, 10:34 PM
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
There are many web apps. Log4j logger is used in all web apps
there are no system.out or system.err
Then where is your catalina.out usage coming from? Tomcat does not itself put
anything
OS : RedHat Linux
Tomcat version : 5.5.20
Am able to configure the logging level at individual war files, by referring to
log4j.properties in web.xml.
Could someone let me know, how to configure the logging level also the file
appender type at global level, please ?
Thanks
From: Jay [mailto:difficult...@yahoo.com]
Subject: Logging configuration in Tomcat
Could someone let me know, how to configure the logging level
also the file appender type at global level, please ?
Not sure what you mean for at global level; if you're asking about Tomcat's
internal
If you're looking for a way to have a central log4j file for all apps, that may
not be easily done. I don't know how it is now, but I remember that in
previous versions of tomcat sharing tomcat's logging was problematic, which I
think may have been due to Commons Logging.
But that's just my
to specify the file size no of counts for
catalina.out, please ?
Thanks
--- On Sun, 1/11/09, Caldarale, Charles R chuck.caldar...@unisys.com wrote:
From: Caldarale, Charles R chuck.caldar...@unisys.com
Subject: RE: Logging configuration in Tomcat
To: Tomcat Users List users@tomcat.apache.org
Date
From: Jay [mailto:difficult...@yahoo.com]
Subject: RE: Logging configuration in Tomcat
My actual problem is that, as it is, catalina.out is growing
Sounds like your webapps are using System.out or System.err for their logging,
which is poor practice. They should be using a proper logging
Asked on behalf of a colleague. I'm sure someone out there has already
done this...
Colleague has a vanilla download of Tomcat 5.5.17. They want to use it
in production, and want to perform daily analysis of accesses. Ideally,
therefore, they want daily log file rotation for the access log.
I
the original
message without making a copy. Thank you.
- Original Message -
From: Peter Crowther [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Wednesday, July 26, 2006 12:07 PM
Subject: Wtd: Logging configuration for Tomcat 5.5.17 to rotate access logs
daily
Asked on behalf
22 matches
Mail list logo
