log4j problem

2003-01-30 Thread De Cesco, Jonathan
Hi all, I was using Log4J with struts1.0 with no problem. When I updated to struts1.1b3, messages from Struts like RequestProcessor Processing a POST request for path url are logged using my webapp log4j configuration file. The problem is I don't want struts to log these messages but it keeps

RE: log4j problem

2003-01-30 Thread Pani, Gourav
You may want to increase your default console setting from DEBUG to WARN. That would eliminate a lot of log messages. -Original Message- From: De Cesco, Jonathan [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 5:09 AM To: '[EMAIL PROTECTED]' Subject: log4j problem Hi all, I

RE: log4j problem

2003-01-30 Thread De Cesco, Jonathan
]] Envoyé : jeudi 30 janvier 2003 14:10 À : 'Struts Users Mailing List' Objet : RE: log4j problem You may want to increase your default console setting from DEBUG to WARN. That would eliminate a lot of log messages. -Original Message- From: De Cesco, Jonathan [mailto:[EMAIL PROTECTED]] Sent

RE: log4j problem

2003-01-30 Thread shirishchandra . sakhare
Subject: RE: log4j problem ok but the real problem is that struts logs an INFO each time a request is processed. My webapp should handle hundreds of simultaneous clients therefore my personal webapps logs are not visible enough. But thanks anyway. -Message d'origine- De : Pani, Gourav

RE: log4j problem

2003-01-30 Thread De Cesco, Jonathan
]] Envoyé : jeudi 30 janvier 2003 14:18 À : [EMAIL PROTECTED] Objet : RE: log4j problem Can you see the originating class for all those struts loggings messages in the logged messages? I mean in log4j ,u can disable the logging per class or package level..And if struts is using log4j, then it must

RE: log4j problem

2003-01-30 Thread Pani, Gourav
Mailing List' Subject: RE: log4j problem Yes I know the originating class that produces logs, it's RequestProcessor. But I didn't know that log4j could exclude class from the logs. Is it configurable in the log4j conf file ? I will look into it, thanks. -Message d'origine- De : [EMAIL

RE: log4j problem

2003-01-30 Thread shirishchandra . sakhare
hirarchies, it will still not change -Original Message- From: gourav.pani [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 2:24 PM To: struts-user Subject: RE: log4j problem i was under the impression that you do exclusion by inclusion. in other words, if you specify

RE: log4j problem

2003-01-30 Thread De Cesco, Jonathan
-Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 30 janvier 2003 14:31 À : [EMAIL PROTECTED] Objet : RE: log4j problem .U can specify log level per logger as well.SO if u want to exclude logging for some packages,U specify a higher log level

RE: log4j problem

2003-01-30 Thread De Cesco, Jonathan
It worked, thank you, my understanding of Log4J was rather limited!! -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 30 janvier 2003 14:31 À : [EMAIL PROTECTED] Objet : RE: log4j problem .U can specify log level per logger as well.SO if u want

Re: log4j problem

2003-01-30 Thread Matthew Meyer
I am having a simmilar problem. I'm useing Struts 1.1b2 within WTE 3.5. The digester and requestProcessor refuse to quit logging not matter what I set the log levels at. I'm guessing I'm just not finding the correct configuration file, but it's really getting annoying. Matt, On Thu, 30 Jan

RE: log4j problem

2003-01-30 Thread De Cesco, Jonathan
Meyer [mailto:[EMAIL PROTECTED]] Envoyé : jeudi 30 janvier 2003 14:45 À : Struts Users Mailing List Objet : Re: log4j problem I am having a simmilar problem. I'm useing Struts 1.1b2 within WTE 3.5. The digester and requestProcessor refuse to quit logging not matter what I set the log levels at. I'm

mysterious log4j problem

2002-08-27 Thread Donald Ball
Did something change between 1.1b1 and 1.1b2 regarding log4j behavior in struts? It's a long shot, but it's worth asking. Our log4j debug statements are disappearing now and the only relevant change we made was to upgrade from 1.1b1 to 1.1b2. I grepped through the struts source and wasn't able to

Re: mysterious log4j problem

2002-08-27 Thread Donald Ball
On 8/27/2002 at 3:16 PM Donald Ball wrote: Did something change between 1.1b1 and 1.1b2 regarding log4j behavior in struts? It's a long shot, but it's worth asking. Our log4j debug statements are disappearing now and the only relevant change we made was to upgrade from 1.1b1 to 1.1b2. I grepped

Re: mysterious log4j problem

2002-08-27 Thread Craig R. McClanahan
On Tue, 27 Aug 2002, Donald Ball wrote: Date: Tue, 27 Aug 2002 15:16:15 -0400 From: Donald Ball [EMAIL PROTECTED] Reply-To: Struts Users Mailing List [EMAIL PROTECTED], [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: mysterious log4j problem Did something change between 1.1b1

Re: mysterious log4j problem

2002-08-27 Thread Craig R. McClanahan
On Tue, 27 Aug 2002, Donald Ball wrote: Date: Tue, 27 Aug 2002 15:54:13 -0400 From: Donald Ball [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: mysterious log4j problem On 8/27/2002 at 12:48 PM Craig R. McClanahan wrote: Have you heeded the comment at the bottom

Re: mysterious log4j problem

2002-08-27 Thread Donald Ball
On 8/27/2002 at 12:48 PM Craig R. McClanahan wrote: Have you heeded the comment at the bottom of the 1.1-b2 download page about picking up the latest commons-logging.jar? It's in the paragraph that starts with bold text Log4J Users Please Note :-). Nope, i was needlessly heedless. :) Thanks