/show_bug.cgi?id=27371
--- Additional Comments From [EMAIL PROTECTED] 2005-08-04 14:57 ---
I found a solution. copy the log4j jar file and rename to another file name,
such as log4j-1.2.6.jar. put the both log4j jar files to WEB-INF lib directory.
--
Configure bugmail: http
/show_bug.cgi?id=27371
--- Additional Comments From [EMAIL PROTECTED] 2005-08-04 15:45 ---
Your solution seems more like black magic to me. What do you think you've
fixed? And what is it about having 2 log4j jars in WEB-INF/lib changes the
thread death behavior? You do realize
Thank-you for your e-mail.
Please note that i will be away from the office starting Wednesday June
29th, returning Thursday July 7th, with no access to email. In my absence,
kindly contact Cheri Dueck at [EMAIL PROTECTED]
Kind Regards,
Natasha Hasmani
Senior Event Manager
Thank-you for your e-mail.
Please note that i will be away from the office starting Wednesday June
29th, returning Thursday July 7th, with no access to email. In my absence,
kindly contact Cheri Dueck at [EMAIL PROTECTED]
Kind Regards,
Natasha Hasmani
Senior Event Manager
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27371.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27371.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Hello,
I have a plug-in which configures log4j on per context basis from
external property file. As result each of my contexts log to its own
file and is configured from property file stored outside of its WAR
file. The system allows log4j.jar and commons-logging.jar in server/lib
or commons/lib
works of course with no log4j files in server/lib common/lib
but I would like to use log4j for server logging as well
Since you know what you are doing, you should identify where:
- Tomcat context classloader would be incorrectly set
- The logger from this context (the container logger) would
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=33711
--- Additional Comments From [EMAIL PROTECTED] 2005-04-06 17:37 ---
What did you test exactly (CVS version ?) ? Still using log4j for everything ?
Do you have any idea on where the reference to the classloader would be kept ?
--
Configure bugmail: http
/show_bug.cgi?id=33711
--- Additional Comments From [EMAIL PROTECTED] 2005-04-06 17:58 ---
(In reply to comment #18)
What did you test exactly (CVS version ?) ? Still using log4j for
everything ?
Do you have any idea on where the reference to the classloader would be
kept ?
I updated
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=34139.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=34139
Summary: org.apache.catalina.realm.RealmBase.main() requires JMX
and log4j
Product: Tomcat 5
Version: 5.5.7
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=33711
Summary: Memory leak (classloader) with Log4J and Single Sign On.
Product: Tomcat 5
Version: 5.5.7
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
issue for restartable webapps, not a log4j issue.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are on the CC list for the bug, or are watching someone who
/show_bug.cgi?id=27371
--- Additional Comments From [EMAIL PROTECTED] 2005-02-09 00:42 ---
Hi!
I'm also experiencing ThreadDeath with Log4j on Tomcat 5.0.28 (bundled with
NetBeans 4.0) when restarting applications. I understand you've already seen a
lot of stack traces in this discussion. So
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27371.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27371.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=27371.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32249.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
Comments From [EMAIL PROTECTED] 2004-11-18 17:35 ---
Created an attachment (id=13491)
-- (http://issues.apache.org/bugzilla/attachment.cgi?id=13491action=view)
fuller documentation patch for tomcat 5.5 logging page
including introduction and jdk logging, revised log4j to include note about
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32249.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32249.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
/show_bug.cgi?id=32249
Summary: Log4j section enhancement for Tomcat Logging page
Product: Tomcat 5
Version: 5.5.4
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P2
Component
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=32249.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.
could be found for logger
(org.apache.catalina.startup.Embedded).
log4j:WARN Please initialize the log4j system properly.
I know there are already a lot of complaints on a lot of newsgroups about
this. But since I'm new to the system, the answers aren't really helpful.
I already tried to change
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-09-22 14:12 ---
Per Jay Paulsen's findings archived at http://marc.theaimsgroup.com/?
t=10957839304r=1w=2, please try adding the Introspector.flush
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-31 20:11 ---
I've got the same exception, but without log4j envolvement. To reproduce try
this:
1. In TC 5.0.27 login to admin application.
2. Under
Hello,
At 2004-01-23 11:54, just 4 minutes after bug number 26372 [1] was
filed, Remy Maucherat threw it out, saying:
This is the old issue of log4j trying to use the previous classloader
(reloading will create a new classloader to load class definitions;
see bug 3888 [2]). Maybe it would
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-06 16:25 ---
I can confirm that the following does _not_ solve the ThreadDeath exception
when Tomcat reloads the context following a class compile
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-06 17:55 ---
It seems to me that tomcat reuses these classloaders and I have a feeling that
when the classloader is being reused. The classloader start
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-06 17:57 ---
What are you basing this on? Any code references would be nice
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-07 00:55 ---
I was looking at the WebappClassLoader class and it contains a started attribute
that is used to determine that if the WebappClassLoader
In relation to bug #26372 Remy wrote:
--- Additional Comments From Remy Maucherat 2004-01-23 11:54 ---
This is the old issue of log4j trying to use the previous classloader=20
(reloading
will create a new classloader to load class definitions; see bug 3888).=20
Maybe it
would be good
At 04:22 PM 8/5/2004, Andy McBride wrote:
Commons logging seems to cache LogFactory instances using its
classloader as a key - perhaps this could be suspect?
Oh, yes indeed.
--
Ceki Gülcü
For log4j documentation consider The complete log4j manual
ISBN: 2970036908 http://www.qos.ch/shop
/show_bug.cgi?id=27371
java.lang.ThreadDeath caused by log4j when reloading Tomcat app
--- Additional Comments From [EMAIL PROTECTED] 2004-08-05 19:36 ---
--- Begin Text by Craig McClanahan ---
The reason that LogFactory instances are stored in a map keyed by
context class loader was to meet
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED
/show_bug.cgi?id=28961
log4j logger proxy patch
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|WONTFIX
/show_bug.cgi?id=28961
log4j logger proxy patch
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution
/show_bug.cgi?id=28961
log4j logger proxy patch
--- Additional Comments From [EMAIL PROTECTED] 2004-05-29 21:27 ---
Please read
http://bugzilla.mozilla.org/page.cgi?id=etiquette.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
--- Additional Comments From [EMAIL PROTECTED] 2004-05-26 19:27 ---
From what I observed, it only changes filename every day, but doesn't deleted
older ones. If so, what is the rolling policy?
-size? what size
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
Summary: provide new Log4J/java2-logging-api proxy loggers class
Product: Tomcat 5
Version: 5.0.24
Platform: All
OS/Version: All
Status: NEW
Severity
/show_bug.cgi?id=28961
provide new Log4J/java2-logging-api proxy loggers class
--- Additional Comments From [EMAIL PROTECTED] 2004-05-13 18:32 ---
this is mainly to delegate to more versatile logging systems,
and also to work around the file logger that doesn't roll the files (risk
running out
Hello Matthew,
We have just added new code to log4j in order to provide a complete
solution to the problem you are describing.
It has several advantages over ContextClassLoaderSelector you
mentioned. For more details, see
http://cvs.apache.org/viewcvs.cgi/logging-log4j/examples/tiny-webapp
I'm using log4j to log application code for several websites,
each of which has at least one WebApp, and some of which have
more than one. I'm configuring log4j with an initialization
servlet (that also does a few other things) from a properties
file using .configureAndWatch(java.io.File
I am using log4j in my WebApplication.
Where I must configurate path or classpath in Tomcat to locate
logXX.properties (properties file of log4j).
I put my propertie file in web-inf\classes but it does not works.
What I need to do
Hi everybody
I'm new in tomcat, and when i instaled the Apache Tomcat/4.1.27 i get the following
warn on stderr.log:
log4j:WARN No appenders could be found for logger
(org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.
I previously installed
of commons-logging.jar?) . I end up with this exception from Jasper2 (attached below). I do not want to use log4j, but If I dare to include log4.jar in the Jasper2 task classloader, another tasks (Xdoclet) becomes aware of it (despite the fact that I use separate Ant classloader for it!) and starts throwing
up with this exception from Jasper2
(attached below). I do not want to use log4j, but If I dare to include log4.jar in
the Jasper2 task classloader, another tasks (Xdoclet) becomes aware of it (despite the
fact that I use separate Ant classloader for it!) and starts throwing log4j-related
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
CC
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
Version|4.0.1 Beta 1
/show_bug.cgi?id=4091
custom host with unpackWARs=true don't expand war automatically - work around fails
log4j!
[EMAIL PROTECTED] changed:
What|Removed |Added
CC
/show_bug.cgi?id=20171
weird: log4j and filter initialization
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Additional
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
--- Additional Comments From [EMAIL PROTECTED] 2002-08-29 06:52 ---
I think making it configurable is a great solution, especially for developers
using IDEs with small monitors. Thank you for taking
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
Summary: Log4J ConsoleAppender System.out.println do not
display on console
Product: Tomcat 4
Version: 4.1.9
Platform: PC
OS/Version: Windows
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
--- Additional Comments From [EMAIL PROTECTED] 2002-08-28 13:56 ---
I uninstalled 4.1.9 and installed 4.0.4. When I start tomcat I get pages and
pages of debug log messages on the console from
/show_bug.cgi?id=12113
Log4J ConsoleAppender System.out.println do not display on console
--- Additional Comments From [EMAIL PROTECTED] 2002-08-29 00:11 ---
Here is the change that was made in the 4.1 Tomcat branch to
stdout/stderr logging:
For those running unix, stdout/stderr has always
][PATCH]commons-logging built without log4j/LogKit
Now, like Costin, I'm starting to think that the 5.0 build is scary.
- Original Message -
From: Steve Downey [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, August 07, 2002 10:00 PM
Subject: [5][PATCH]commons-logging built
If you follow the directions in BUILDING.txt, it's not necessary to download
log4j or LogKit. BUILDING.txt asks for a nightly build of commons-logging,
which would have been built against log4j and LogKit. If they aren't present
at runtime, they won't be used as the implementation of commons
At 14:42 14.06.2002 -0700, [EMAIL PROTECTED] wrote:
I recently enabled JMX support for jk, and one of the things it's
doing is detect if log4j is available and enable the log4j JMX.
There are few problems - and this is a deeper problem, that affects
the use of log4j as 'main' logger for tomcat
I recently enabled JMX support for jk, and one of the things it's
doing is detect if log4j is available and enable the log4j JMX.
There are few problems - and this is a deeper problem, that affects
the use of log4j as 'main' logger for tomcat.
The first problem is conflicts in the generated
Read the log4j manual.
http://jakarta.apache.org/log4j/docs/manual.html
From: Kenny Ma [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Log4J ?
Date: Fri, 14 Sep 2001 10:03:18 +0800
Can anyone tell me how to use Log4J ?
the sample is
cat.debug(Hello world
Can anyone tell me how to use Log4J ?
the sample is
cat.debug(Hello world.);
cat.info(What a beatiful day.);
so, what is the different if i use
System.err.println(Hello world.); ???
Both are output to standout...
How to use Log4J more easy ? Thanks
/* Kenny Ma
[EMAIL PROTECTED] */
Hi Goug,
The user manual in the just released log4j 1.1.2 has a section on default
initialization, in particular initialization under Tomcat. Be sure to read:
http://jakarta.apache.org/log4j/docs/manual.html#defaultInit
Hope this helps, Ceki
Hi,
I am trying to replace
static Log class for this very reason.
On Saturday, June 9, 2001, at 11:54 AM, Ceki Gülcü wrote:
Hi Goug,
The user manual in the just released log4j 1.1.2 has a section on
default initialization, in particular initialization under Tomcat. Be
sure to read:
http://jakarta.apache.org/log4j
At 23:04 21.04.2001 -0500, you wrote:
Ceki Glc wrote:
One important point to remember is that each webapp classloader could load a fresh
copy of log4j so that each webapp has its own logging universe.
This would significantly increase the memory footprint required for logging in the
JVM
My two cents as a Log4J User.
I use Log4J in my servlets and I think it great. Logging has never been so easy.
One issue though, the Configurator class holds it data in a Static variable so
two servlets inside the same JVM will each over write the others config. Even
since I implemented Log4J I
At 21:40 21.04.2001 -0700, you wrote:
On Sat, 21 Apr 2001, Glenn Nielsen wrote:
Ceki Glc wrote:
One important point to remember is that each
webapp classloader could load a fresh copy of log4j so that each
webapp has its own logging universe.
This would significantly increase
there, and it was configurable per component. My cohort converted the whole thing to
use Log4J in two days, and I was even happier after that. We had started with the
retrofitting solution, but it was easier in the end to define a standard way to get
the Category, and then cut and paste that code
On Sat, 21 Apr 2001, Glenn Nielsen wrote:
Ceki,
This is welcome news!
It isn't clear to me whether the standard servlet API logging methods
could use log4j behind the scense to do logging. This would be very
nice, especially if you could configure log4j logging for each scope
At 17:45 21.04.2001 -0700, you wrote:
My two cents as a Log4J User.
I use Log4J in my servlets and I think it great. Logging has never been so easy.
One issue though, the Configurator class holds it data in a Static variable so
two servlets inside the same JVM will each over write the others
Craig R. McClanahan wrote:
On Sat, 21 Apr 2001, Glenn Nielsen wrote:
Ceki Gülcü wrote:
One important point to remember is that each
webapp classloader could load a fresh copy of log4j so that each
webapp has its own logging universe.
This would significantly increase
Hello,
I am toying with the idea of migrating catalina logging to log4j. Let me begin by
saying that I am far from being familiar with catalina internals but I am getting
there slowly.
After a short initial study and some experimentation, here are some tentative
conclusions:
1) The way
1 - 100 of 101 matches
Mail list logo
