You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Rob Walker (JIRA)" <ji...@apache.org> on 2008/10/15 11:25:44 UTC
[jira] Created: (FELIX-771) Jetty 6 is "verbose" on the log
Jetty 6 is "verbose" on the log
-------------------------------
Key: FELIX-771
URL: https://issues.apache.org/jira/browse/FELIX-771
Project: Felix
Issue Type: Bug
Components: HTTP Service
Reporter: Rob Walker
Priority: Minor
The latest Jetty6 seems quite verbose on the log, including messages that are borderline diagnostic/trace e.g.
---+---
org.mortbay.log:Logging to org.mortbay.log via org.apache.felix.http.jetty.LogServiceLog
org.mortbay.log:Init SecureRandom.
org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionIdManager@3020ad
org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionManager@7f4ec
org.mortbay.log:starting OsgiServletHandler@60e128
org.mortbay.log:started OsgiServletHandler@60e128
org.mortbay.log:starting SessionHandler@5e1077
org.mortbay.log:started SessionHandler@5e1077
org.mortbay.log:starting org.mortbay.jetty.servlet.Context@134e4fb{/,null}
org.mortbay.log:starting ErrorHandler@18b3364
org.mortbay.log:started ErrorHandler@18b3364
org.mortbay.log:started org.mortbay.jetty.servlet.Context@134e4fb{/,null}
org.mortbay.log:jetty-6.1.x
org.mortbay.log:started Realm[OSGi HTTP Service Realm]==[]
org.mortbay.log:started org.mortbay.thread.QueuedThreadPool@bc8e1e
org.mortbay.log:starting Server@11671b2
org.mortbay.log:started org.mortbay.jetty.nio.SelectChannelConnector$1@2bc3f5
org.mortbay.log:Started SelectChannelConnector@0.0.0.0:8080
org.mortbay.log:started SelectChannelConnector@0.0.0.0:8080
org.mortbay.log:started Server@11671b2
org.mortbay.log:started /xmlrpc/*
org.mortbay.log:EOF
org.mortbay.log:EOF
org.mortbay.log:EOF
org.mortbay.log:EOF
---+---
These go to OSGI LogService if present, or System.out if not.
Couple of options to investigate:
* allow better control of Jetty log level through properties if feasible
* possibly include more formalized "prefix" to messages if not, to make for easier external filtering
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-771) Jetty 6 is "verbose" on the log
Posted by "Sten Roger Sandvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sten Roger Sandvik resolved FELIX-771.
--------------------------------------
Resolution: Fixed
> Jetty 6 is "verbose" on the log
> -------------------------------
>
> Key: FELIX-771
> URL: https://issues.apache.org/jira/browse/FELIX-771
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Affects Versions: http-2.0.0
> Reporter: Rob Walker
> Assignee: Sten Roger Sandvik
> Priority: Minor
> Fix For: http-2.0.0
>
>
> The latest Jetty6 seems quite verbose on the log, including messages that are borderline diagnostic/trace e.g.
> ---+---
> org.mortbay.log:Logging to org.mortbay.log via org.apache.felix.http.jetty.LogServiceLog
> org.mortbay.log:Init SecureRandom.
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionIdManager@3020ad
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionManager@7f4ec
> org.mortbay.log:starting OsgiServletHandler@60e128
> org.mortbay.log:started OsgiServletHandler@60e128
> org.mortbay.log:starting SessionHandler@5e1077
> org.mortbay.log:started SessionHandler@5e1077
> org.mortbay.log:starting org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:starting ErrorHandler@18b3364
> org.mortbay.log:started ErrorHandler@18b3364
> org.mortbay.log:started org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:jetty-6.1.x
> org.mortbay.log:started Realm[OSGi HTTP Service Realm]==[]
> org.mortbay.log:started org.mortbay.thread.QueuedThreadPool@bc8e1e
> org.mortbay.log:starting Server@11671b2
> org.mortbay.log:started org.mortbay.jetty.nio.SelectChannelConnector$1@2bc3f5
> org.mortbay.log:Started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started Server@11671b2
> org.mortbay.log:started /xmlrpc/*
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> ---+---
> These go to OSGI LogService if present, or System.out if not.
> Couple of options to investigate:
> * allow better control of Jetty log level through properties if feasible
> * possibly include more formalized "prefix" to messages if not, to make for easier external filtering
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-771) Jetty 6 is "verbose" on the log
Posted by "Sten Roger Sandvik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sten Roger Sandvik updated FELIX-771:
-------------------------------------
Affects Version/s: http-2.0.0
Fix Version/s: http-2.0.0
Assignee: Sten Roger Sandvik
Classifies all info loggig on jetty as debug. Added "one-line" log on startup.
> Jetty 6 is "verbose" on the log
> -------------------------------
>
> Key: FELIX-771
> URL: https://issues.apache.org/jira/browse/FELIX-771
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Affects Versions: http-2.0.0
> Reporter: Rob Walker
> Assignee: Sten Roger Sandvik
> Priority: Minor
> Fix For: http-2.0.0
>
>
> The latest Jetty6 seems quite verbose on the log, including messages that are borderline diagnostic/trace e.g.
> ---+---
> org.mortbay.log:Logging to org.mortbay.log via org.apache.felix.http.jetty.LogServiceLog
> org.mortbay.log:Init SecureRandom.
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionIdManager@3020ad
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionManager@7f4ec
> org.mortbay.log:starting OsgiServletHandler@60e128
> org.mortbay.log:started OsgiServletHandler@60e128
> org.mortbay.log:starting SessionHandler@5e1077
> org.mortbay.log:started SessionHandler@5e1077
> org.mortbay.log:starting org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:starting ErrorHandler@18b3364
> org.mortbay.log:started ErrorHandler@18b3364
> org.mortbay.log:started org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:jetty-6.1.x
> org.mortbay.log:started Realm[OSGi HTTP Service Realm]==[]
> org.mortbay.log:started org.mortbay.thread.QueuedThreadPool@bc8e1e
> org.mortbay.log:starting Server@11671b2
> org.mortbay.log:started org.mortbay.jetty.nio.SelectChannelConnector$1@2bc3f5
> org.mortbay.log:Started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started Server@11671b2
> org.mortbay.log:started /xmlrpc/*
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> ---+---
> These go to OSGI LogService if present, or System.out if not.
> Couple of options to investigate:
> * allow better control of Jetty log level through properties if feasible
> * possibly include more formalized "prefix" to messages if not, to make for easier external filtering
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-771) Jetty 6 is "verbose" on the log
Posted by "Rob Walker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Walker updated FELIX-771:
-----------------------------
Issue Type: Improvement (was: Bug)
> Jetty 6 is "verbose" on the log
> -------------------------------
>
> Key: FELIX-771
> URL: https://issues.apache.org/jira/browse/FELIX-771
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Minor
>
> The latest Jetty6 seems quite verbose on the log, including messages that are borderline diagnostic/trace e.g.
> ---+---
> org.mortbay.log:Logging to org.mortbay.log via org.apache.felix.http.jetty.LogServiceLog
> org.mortbay.log:Init SecureRandom.
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionIdManager@3020ad
> org.mortbay.log:started org.mortbay.jetty.servlet.HashSessionManager@7f4ec
> org.mortbay.log:starting OsgiServletHandler@60e128
> org.mortbay.log:started OsgiServletHandler@60e128
> org.mortbay.log:starting SessionHandler@5e1077
> org.mortbay.log:started SessionHandler@5e1077
> org.mortbay.log:starting org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:starting ErrorHandler@18b3364
> org.mortbay.log:started ErrorHandler@18b3364
> org.mortbay.log:started org.mortbay.jetty.servlet.Context@134e4fb{/,null}
> org.mortbay.log:jetty-6.1.x
> org.mortbay.log:started Realm[OSGi HTTP Service Realm]==[]
> org.mortbay.log:started org.mortbay.thread.QueuedThreadPool@bc8e1e
> org.mortbay.log:starting Server@11671b2
> org.mortbay.log:started org.mortbay.jetty.nio.SelectChannelConnector$1@2bc3f5
> org.mortbay.log:Started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started SelectChannelConnector@0.0.0.0:8080
> org.mortbay.log:started Server@11671b2
> org.mortbay.log:started /xmlrpc/*
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> org.mortbay.log:EOF
> ---+---
> These go to OSGI LogService if present, or System.out if not.
> Couple of options to investigate:
> * allow better control of Jetty log level through properties if feasible
> * possibly include more formalized "prefix" to messages if not, to make for easier external filtering
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.