Bugzilla – Full Text Bug Listing
| Summary: | Debug messages being written by Jetty | ||
|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Chris Goldthorpe <cgold> |
| Component: | Server-Side | Assignee: | Simon Archer <sja.eclipse> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hjg.com.ar, tjwatson |
| Version: | 3.8.0 Juno | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Chris Goldthorpe
Correction: The messages were written to the console, not the log. The fix to Bug 363584 is not required to reproduce the problem. Simon A. please have a look. Same here. I experienced this after migrating a RCP product that uses the Eclipse help system (org.eclipse.help.*) from Indigo (3.7) to Kepler (4.3). Tons of DEBUG logs are written to stderr when I access the Help. To add to the previous: It would seem that the StdErrLog instance is being created with LEVEL_DEBUG (or less), instead of the (expected?) default LEVEL_INFO.
A small trimmed sample:
19:00:34.222 [qtp14173363-43] DEBUG org.eclipse.jetty.http.HttpParser - filled 637/637
19:00:34.223 [qtp14173363-43 - /help/advanced/tocView.jsp?view=toc] DEBUG org.eclipse.jetty.server.Server - REQUEST /help/advanced/tocView.jsp on
19:00:34.223 [qtp14173363-43 - /help/advanced/tocView.jsp?view=toc] DEBUG o.e.jetty.servlet.ServletHandler - servlet /help||/advanced/tocView.jsp
19:00:34.223 [qtp14173363-40 - /help/advanced/tocToolbar.jsp] DEBUG o.e.j.server.handler.ContextHandler - scope /help||/advanced/tocToolbar.jsp @
19:00:34.224 [qtp14173363-43] DEBUG o.e.jetty.server.AsyncHttpConnection - Enabled read interest SCEP@124ec4a{l(/127.0.0.1:17881)<->r(/127.0.0.1:
I don't have any jetty-logging.properties in my classpath and my System.getProperties() returns nothing related with this. For completenes, here's the full keys list:
applicationXMI
awt.toolkit
eclipse.commands
eclipse.consoleLog
eclipse.home.location
eclipse.launcher
eclipse.launcher.name
eclipse.product
eclipse.startTime
equinox.use.ds
file.encoding
file.encoding.pkg
file.separator
gosh.args
java.awt.graphicsenv
java.awt.printerjob
java.class.path
java.class.version
java.endorsed.dirs
java.ext.dirs
java.home
java.io.tmpdir
java.library.path
java.runtime.name
java.runtime.version
java.specification.name
java.specification.vendor
java.specification.version
java.vendor
java.vendor.url
java.vendor.url.bug
java.version
java.vm.info
java.vm.name
java.vm.specification.name
java.vm.specification.vendor
java.vm.specification.version
java.vm.vendor
java.vm.version
line.separator
org.eclipse.equinox.launcher.splash.location
org.osgi.framework.executionenvironment
org.osgi.framework.language
org.osgi.framework.os.name
org.osgi.framework.os.version
org.osgi.framework.processor
org.osgi.framework.system.capabilities
org.osgi.framework.system.packages
org.osgi.framework.uuid
org.osgi.framework.vendor
org.osgi.framework.version
org.osgi.supports.framework.extension
org.osgi.supports.framework.fragment
org.osgi.supports.framework.requirebundle
os.arch
os.name
os.version
osgi.arch
osgi.bundles
osgi.bundles.defaultStartLevel
osgi.bundlestore
osgi.checkConfiguration
osgi.configuration.area
osgi.configuration.cascaded
osgi.dev
osgi.framework
osgi.framework.shape
osgi.framework.version
osgi.install.area
osgi.instance.area
osgi.logfile
osgi.manifest.cache
osgi.nl
osgi.nl.user
osgi.os
osgi.requiredJavaVersion
osgi.splashLocation
osgi.splashPath
osgi.syspath
osgi.tracefile
osgi.ws
path.separator
sun.arch.data.model
sun.boot.class.path
sun.boot.library.path
sun.cpu.endian
sun.cpu.isalist
sun.desktop
sun.io.unicode.encoding
sun.java.command
sun.java.launcher
sun.jnu.encoding
sun.management.compiler
sun.os.patch.level
user.country
user.dir
user.home
user.language
user.name
user.script
user.timezone
user.variant
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |