RE : RE : Logging to console not working with Tomcat 4.1.9
-- but of course it's still really easy to use tail -f $CATALINA_HOME/logs/catalina.out to monitor the output. On recent Windows OSs (but not 98) you can accomplish the same thing by installing CYGWIN and using it's tail command. The problem is when using an IDE like Eclipse. I don't have room on the screen for another log window. The good news is I just read on the bug report that a new feature has been added to the nightly build which will allow this behavior to be turned on or off, thereby allowing output to the console! I find this extremely useful for debugging with Eclipse. Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
BUG: Logging to console not working with Tomcat 4.1.9
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 the apache tools I'm using (Struts, messenger, etc.) and my own classes. I uninstalled 4.0.4 and installed 4.1.9 and when I run it I only get 4 lines. I haven't changed anything in my code or the tomcat directory. So I'm 100% positive something is broken in 4.1.9 regarding outputing messages to the console. For now I've switched back to 4.0.4 and logging to the console is working just fine. I filed a bug on Bugzilla, I'll post any responses I get to the mailing list. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12113 Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Logging to console not working with Tomcat 4.1.9
So you mean output to System.out System.err? As of 4.1.9 that's been changed to go to a log file. - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:20 AM Subject: BUG: Logging to console not working with Tomcat 4.1.9 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 the apache tools I'm using (Struts, messenger, etc.) and my own classes. I uninstalled 4.0.4 and installed 4.1.9 and when I run it I only get 4 lines. I haven't changed anything in my code or the tomcat directory. So I'm 100% positive something is broken in 4.1.9 regarding outputing messages to the console. For now I've switched back to 4.0.4 and logging to the console is working just fine. I filed a bug on Bugzilla, I'll post any responses I get to the mailing list. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12113 Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE : Logging to console not working with Tomcat 4.1.9
No I mean log4j's ConsoleAppender. So are you saying that Tomcat now routes the log4j ConsoleAppender to a logfile as well? If so I think that's a big problem for debugging. While running my app in the IDE I want to see all the console output without having to switch to a text editor and reload the log file. Can I configure Tomcat 4.1.9 to do this?? Michael -Original Message- From: Tony LaPaso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 4:38 PM To: Tomcat Users List Subject: Re: Logging to console not working with Tomcat 4.1.9 So you mean output to System.out System.err? As of 4.1.9 that's been changed to go to a log file. - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:20 AM Subject: BUG: Logging to console not working with Tomcat 4.1.9 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 the apache tools I'm using (Struts, messenger, etc.) and my own classes. I uninstalled 4.0.4 and installed 4.1.9 and when I run it I only get 4 lines. I haven't changed anything in my code or the tomcat directory. So I'm 100% positive something is broken in 4.1.9 regarding outputing messages to the console. For now I've switched back to 4.0.4 and logging to the console is working just fine. I filed a bug on Bugzilla, I'll post any responses I get to the mailing list. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12113 Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Logging to console not working with Tomcat 4.1.9
Well, honestly, I don't know about log4j. I know that prior to v4.1.9 I would use System.out/err to do light logging to the console and as of v4.1.9 it quit working. I'm not sure if System.out/err are routed to log4j. sorry... - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:47 AM Subject: RE : Logging to console not working with Tomcat 4.1.9 No I mean log4j's ConsoleAppender. So are you saying that Tomcat now routes the log4j ConsoleAppender to a logfile as well? If so I think that's a big problem for debugging. While running my app in the IDE I want to see all the console output without having to switch to a text editor and reload the log file. Can I configure Tomcat 4.1.9 to do this?? Michael -Original Message- From: Tony LaPaso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 4:38 PM To: Tomcat Users List Subject: Re: Logging to console not working with Tomcat 4.1.9 So you mean output to System.out System.err? As of 4.1.9 that's been changed to go to a log file. - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:20 AM Subject: BUG: Logging to console not working with Tomcat 4.1.9 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 the apache tools I'm using (Struts, messenger, etc.) and my own classes. I uninstalled 4.0.4 and installed 4.1.9 and when I run it I only get 4 lines. I haven't changed anything in my code or the tomcat directory. So I'm 100% positive something is broken in 4.1.9 regarding outputing messages to the console. For now I've switched back to 4.0.4 and logging to the console is working just fine. I filed a bug on Bugzilla, I'll post any responses I get to the mailing list. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12113 Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Logging to console not working with Tomcat 4.1.9
I think that it could be a problem with the commons-logging API used by tomcat, struts, ... Theoricaly, commons-logging should discover itself the logging lib used(log4j, JDK 1.4, ...) but you can force it using a property files. See the commons logging doc to know more about this property file. Arno -Message d'origine- De: Tony LaPaso [mailto:[EMAIL PROTECTED]] Date: mercredi 28 août 2002 17:00 À: Tomcat Users List Objet: Re: Logging to console not working with Tomcat 4.1.9 Well, honestly, I don't know about log4j. I know that prior to v4.1.9 I would use System.out/err to do light logging to the console and as of v4.1.9 it quit working. I'm not sure if System.out/err are routed to log4j. sorry... - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:47 AM Subject: RE : Logging to console not working with Tomcat 4.1.9 No I mean log4j's ConsoleAppender. So are you saying that Tomcat now routes the log4j ConsoleAppender to a logfile as well? If so I think that's a big problem for debugging. While running my app in the IDE I want to see all the console output without having to switch to a text editor and reload the log file. Can I configure Tomcat 4.1.9 to do this?? Michael -Original Message- From: Tony LaPaso [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 4:38 PM To: Tomcat Users List Subject: Re: Logging to console not working with Tomcat 4.1.9 So you mean output to System.out System.err? As of 4.1.9 that's been changed to go to a log file. - Original Message - From: Michael [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, August 28, 2002 9:20 AM Subject: BUG: Logging to console not working with Tomcat 4.1.9 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 the apache tools I'm using (Struts, messenger, etc.) and my own classes. I uninstalled 4.0.4 and installed 4.1.9 and when I run it I only get 4 lines. I haven't changed anything in my code or the tomcat directory. So I'm 100% positive something is broken in 4.1.9 regarding outputing messages to the console. For now I've switched back to 4.0.4 and logging to the console is working just fine. I filed a bug on Bugzilla, I'll post any responses I get to the mailing list. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12113 Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE : Logging to console not working with Tomcat 4.1.9
I think that it could be a problem with the commons-logging API used by tomcat, struts, ... Theoricaly, commons-logging should discover itself the logging lib used(log4j, JDK 1.4, ...) but you can force it using a property files. See the commons logging doc to know more about this property file. I don't think this is the problem for two reasons: 1) I have the same problem with my logging and I'm not using Apache's logging API. 2) It works fine with Tomcat 4.0.4 and doesn't work with 4.1.9. I know 4.1.9 was modified so that stdout err do not go to the console. It looks like they prevented the ConsoleAppender from going to the console too. Not sure at this point if it's a bug or by design. Michael -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: RE : Logging to console not working with Tomcat 4.1.9
On Wed, 28 Aug 2002, Michael wrote: Date: Wed, 28 Aug 2002 16:47:39 +0200 From: Michael [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Subject: RE : Logging to console not working with Tomcat 4.1.9 No I mean log4j's ConsoleAppender. So are you saying that Tomcat now routes the log4j ConsoleAppender to a logfile as well? If so I think that's a big problem for debugging. While running my app in the IDE I want to see all the console output without having to switch to a text editor and reload the log file. Can I configure Tomcat 4.1.9 to do this?? IIRC, the ConsoleAppender in Log4J just writes to System.out or System.err, so Tomcat redirecting those streams will affect Log4J as well. On Unix systems, Tomcat has *always* redirected console output to a file -- but of course it's still really easy to use tail -f $CATALINA_HOME/logs/catalina.out to monitor the output. On recent Windows OSs (but not 98) you can accomplish the same thing by installing CYGWIN and using it's tail command. Michael Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
