Skip to main content
Jump to: navigation, search

Difference between revisions of "Talk:Jetty/Feature/Jetty Logging"

(New page: This article currently has this entry: ''Changing log level in <tt>etc/jetty.xml</tt>'' <source lang="xml"> <Get class="org.eclipse.jetty.util.log.Log" name="log"> <Call name="setDe...)
 
(Order of logging detail: new section)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 +
==setDebugEnabled missing==
 
This article currently has this entry:
 
This article currently has this entry:
  
 
+
...................
''Changing log level in <tt>etc/jetty.xml</tt>''
+
:''Changing log level in <tt>etc/jetty.xml</tt>''
  
 
<source lang="xml">
 
<source lang="xml">
Line 11: Line 12:
 
</Get>
 
</Get>
 
</source>
 
</source>
 +
...................
 +
 +
Class [http://download.eclipse.org/jetty/stable-8/apidocs/org/eclipse/jetty/util/log/Log.html org.eclipse.jetty.util.log.Log] does not have a method called ''setDebugEnabled''. Can someone fix the example, and say what it is good for? --[[User:Mondgesicht.gmx.net|Abdull]] 12:33, 28 August 2012 (UTC)
 +
 +
==Different System Properties==
 +
This article, under section [[Jetty/Feature/Jetty_Logging#Configuring_Jetty_StdErrLog|''Configuring Jetty StdErrLog'']] names system properties and system property values which are '''different''' from those mentioned in the [http://download.eclipse.org/jetty/stable-8/apidocs/org/eclipse/jetty/util/log/StdErrLog.html Javadoc documentation for StdErrLog] (e.g. wiki pages mentions logging levels ''INFO, DEBUG, WARN, NONE'', but Javadoc page mentions logging levels ''ALL, DEBUG, INFO, WARN'') ... (e.g. wiki page mentions system property <code>org.eclipse.jetty.util.log.stderr.LONG=<boolean></code>, but Javadoc mentions system property <code>org.eclipse.jetty.util.log.LONG=<boolean></code> without the <code>stderr</code> part). --[[User:Mondgesicht.gmx.net|Abdull]] 13:07, 28 August 2012 (UTC)
  
 +
== Order of logging detail ==
  
Class [http://download.eclipse.org/jetty/stable-8/apidocs/org/eclipse/jetty/util/log/Log.html org.eclipse.jetty.util.log.Log] does not have a method called ''setDebugEnabled''. Can someone fix the example, and say what it actually does? --[[User:Mondgesicht.gmx.net|Abdull]] 12:33, 28 August 2012 (UTC)
+
What is the order of log details? Is it  INFO -> DEBUG -> WARN -> NONE, (from highest detail to lowest detail), as this article hints? --[[User:Mondgesicht.gmx.net|Abdull]] 22:52, 15 September 2012 (UTC)

Latest revision as of 18:52, 15 September 2012

setDebugEnabled missing

This article currently has this entry:

...................

Changing log level in etc/jetty.xml
<Get class="org.eclipse.jetty.util.log.Log" name="log">
    <Call name="setDebugEnabled">
        <Arg type="boolean">true</Arg>
    </Call>
</Get>

...................

Class org.eclipse.jetty.util.log.Log does not have a method called setDebugEnabled. Can someone fix the example, and say what it is good for? --Abdull 12:33, 28 August 2012 (UTC)

Different System Properties

This article, under section Configuring Jetty StdErrLog names system properties and system property values which are different from those mentioned in the Javadoc documentation for StdErrLog (e.g. wiki pages mentions logging levels INFO, DEBUG, WARN, NONE, but Javadoc page mentions logging levels ALL, DEBUG, INFO, WARN) ... (e.g. wiki page mentions system property org.eclipse.jetty.util.log.stderr.LONG=<boolean>, but Javadoc mentions system property org.eclipse.jetty.util.log.LONG=<boolean> without the stderr part). --Abdull 13:07, 28 August 2012 (UTC)

Order of logging detail

What is the order of log details? Is it INFO -> DEBUG -> WARN -> NONE, (from highest detail to lowest detail), as this article hints? --Abdull 22:52, 15 September 2012 (UTC)

Back to the top