Re: Turning on debugging in Tomcat 5.5

2005-10-10 Thread Marcus Franke 
On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote:
 
 James Rome [EMAIL PROTECTED] wrote in message 
 news:[EMAIL PROTECTED]
  Most of the installed Tomcat classes have something like
  container.isDebugEnabled() {...}
 
  How do I enable these debug statements in Tomcat 5.5?
 
 
 I'll assume that you are using Juli.  If you are using log4j, compare what 
 I'm saying to http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html 
 to see what you need to do.
 
 First you edit $CATALINA_HOME/conf/logging.properties and add and something 
 like:
   
 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp].level 
 = FINE
 

Would this control the logging of the tomcat server itsel, too?

Returning to my previous mail, if I activate connectionTimeout
in the asp13 connector tomcat starts to pollute my catalina.out
with messages about timedout connections.

I know that there are connections which tend to timeout, such is life, 
but its a waste of time and storage when tomcat itself informs we
about that fact :)

Looking inside properties file I find the default log level and it
is:

# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers.  For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level= INFO

So, I guess, if I use something like .level=WARN the pollution
of catalina.out may will stop?



Regards,
Marcus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Turning on debugging in Tomcat 5.5

2005-10-10 Thread Marcus Franke 
On Mon, Oct 10, 2005 at 04:41:32PM +0200, Marcus Franke wrote:
 On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote:
  
 
 # Default global logging level.
 # This specifies which kinds of events are logged across
 # all loggers.  For any given facility this global level
 # can be overriden by a facility specific level
 # Note that the ConsoleHandler also has a separate level
 # setting to limit messages printed to the console.
 .level= INFO
 
 So, I guess, if I use something like .level=WARN the pollution
 of catalina.out may will stop?

Ok, had a deeper look inside the tomcat startup scripts on my
RHEL box and catalina.out is written as a redirect of the
tomcat stdout.

So, my next guess is, java.util.logging.ConsoleHandler.level = INFO
could be the right paramter to change?


Sorry, it seems Im not as half as familliar with this stuff
as I should be :(



Marcus

-- 

What terrible way to die.
There are no good ways.
-- Sulu and Kirk, That Which Survives, stardate unknown

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Turning on debugging in Tomcat 5.5

2005-10-10 Thread Marcus Franke 
On Mon, Oct 10, 2005 at 05:20:07PM +0200, Marcus Franke wrote:
 On Mon, Oct 10, 2005 at 04:41:32PM +0200, Marcus Franke wrote:
  On Fri, Oct 07, 2005 at 09:28:23PM -0700, Bill Barker wrote:
   
  
  # Default global logging level.
  # This specifies which kinds of events are logged across
  # all loggers.  For any given facility this global level
  # can be overriden by a facility specific level
  # Note that the ConsoleHandler also has a separate level
  # setting to limit messages printed to the console.
  .level= INFO
  
  So, I guess, if I use something like .level=WARN the pollution
  of catalina.out may will stop?
 
 Ok, had a deeper look inside the tomcat startup scripts on my
 RHEL box and catalina.out is written as a redirect of the
 tomcat stdout.
 
 So, my next guess is, java.util.logging.ConsoleHandler.level = INFO
 could be the right paramter to change?
 

oh no, neither of these points stops my tomcat from being extremly
talkativ.

Any other hints or suggestions how to silence the tomcat?



Marcus

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Turning on debugging in Tomcat 5.5

2005-10-07 Thread Bill Barker 

James Rome [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Most of the installed Tomcat classes have something like
 container.isDebugEnabled() {...}

 How do I enable these debug statements in Tomcat 5.5?


I'll assume that you are using Juli.  If you are using log4j, compare what 
I'm saying to http://jakarta.apache.org/tomcat/tomcat-5.5-doc/logging.html 
to see what you need to do.

First you edit $CATALINA_HOME/conf/logging.properties and add and something 
like:
  org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp].level 
= FINE

s/Catalina/EngineName/ s/localhost/my.host.name/

Of course, if you really want to fill up your logs, you can do something 
like:
   org.apache.catalina.level = FINE



 Thanks,
 Jim 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Turning on debugging in Tomcat 5.5

2005-10-06 Thread James Rome 
Most of the installed Tomcat classes have something like
container.isDebugEnabled() {...}

How do I enable these debug statements in Tomcat 5.5?

Thanks,
Jim


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]