Community
Participate
Working Groups
I was using 4.0 SDK I20100610-2220 and on one occasion when a javadoc hover appeared in the java editor, apparently the jetty server started and logged to the console. bash-3.2$ 10:52:53.099 [Start Help Server] INFO org.mortbay.log - Logging to Logger[org.mortbay.log] via org.mortbay.log.Slf4jLog 10:52:53.159 [Start Help Server] DEBUG org.mortbay.log - Container Server@7d537d53 + SelectChannelConnector@0.0.0.0:51041 as connector 10:52:53.199 [Start Help Server] DEBUG org.mortbay.log - filterNameMap=null 10:52:53.200 [Start Help Server] DEBUG org.mortbay.log - pathFilters=null 10:52:53.200 [Start Help Server] DEBUG org.mortbay.log - servletFilterMap=null 10:52:53.201 [Start Help Server] DEBUG org.mortbay.log - servletPathMap={/*=org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305} 10:52:53.201 [Start Help Server] DEBUG org.mortbay.log - servletNameMap={org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305=org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305} 10:52:53.202 [Start Help Server] DEBUG org.mortbay.log - Container Server@7d537d53 + org.mortbay.jetty.servlet.Context@7e0f7e0f{/help,null} as handler 10:52:53.203 [Start Help Server] DEBUG org.mortbay.log - Container ServletHandler@27002700 + org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305 as servlet 10:52:53.203 [Start Help Server] DEBUG org.mortbay.log - Container ServletHandler@27002700 + (S=org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305,[/*]) as servletMapping 10:52:53.204 [Start Help Server] DEBUG org.mortbay.log - Container SessionHandler@6bd46bd4 + ServletHandler@27002700 as handler 10:52:53.204 [Start Help Server] DEBUG org.mortbay.log - Container SessionHandler@6bd46bd4 + org.mortbay.jetty.servlet.HashSessionManager@64aa64aa as sessionManager 10:52:53.205 [Start Help Server] DEBUG org.mortbay.log - Container org.mortbay.jetty.servlet.Context@7e0f7e0f{/help,null} + SessionHandler@6bd46bd4 as handler 10:52:53.205 [Start Help Server] INFO org.mortbay.log - jetty-6.1.x 10:52:53.212 [Start Help Server] DEBUG org.mortbay.log - Container Server@7d537d53 + org.mortbay.thread.QueuedThreadPool@5dfa5dfa as threadpool 10:52:53.213 [Start Help Server] DEBUG org.mortbay.log - started org.mortbay.thread.QueuedThreadPool@5dfa5dfa 10:52:53.221 [Start Help Server] DEBUG org.mortbay.log - Container org.mortbay.jetty.servlet.Context@7e0f7e0f{/help,null} + ErrorHandler@5c8c5c8c as errorHandler 10:52:53.222 [Start Help Server] DEBUG org.mortbay.log - Container Server@7d537d53 + org.mortbay.jetty.servlet.HashSessionIdManager@69cd69cd as sessionIdManager 10:52:53.223 [Start Help Server] DEBUG org.mortbay.log - Init SecureRandom. 10:52:53.224 [Start Help Server] DEBUG org.mortbay.log - started org.mortbay.jetty.servlet.HashSessionIdManager@69cd69cd 10:52:53.224 [Start Help Server] DEBUG org.mortbay.log - started org.mortbay.jetty.servlet.HashSessionManager@64aa64aa 10:52:53.225 [Start Help Server] DEBUG org.mortbay.log - filterNameMap=null 10:52:53.225 [Start Help Server] DEBUG org.mortbay.log - pathFilters=null 10:52:53.226 [Start Help Server] DEBUG org.mortbay.log - servletFilterMap=null 10:52:53.226 [Start Help Server] DEBUG org.mortbay.log - servletPathMap={/*=org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305} 10:52:53.226 [Start Help Server] DEBUG org.mortbay.log - servletNameMap={org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305=org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305} 10:52:53.227 [Start Help Server] DEBUG org.mortbay.log - starting ServletHandler@27002700 10:52:53.227 [Start Help Server] DEBUG org.mortbay.log - started ServletHandler@27002700 10:52:53.228 [Start Help Server] DEBUG org.mortbay.log - starting SessionHandler@6bd46bd4 10:52:53.228 [Start Help Server] DEBUG org.mortbay.log - started SessionHandler@6bd46bd4 10:52:53.229 [Start Help Server] DEBUG org.mortbay.log - starting org.mortbay.jetty.servlet.Context@7e0f7e0f{/help,null} 10:52:53.229 [Start Help Server] DEBUG org.mortbay.log - starting ErrorHandler@5c8c5c8c 10:52:53.229 [Start Help Server] DEBUG org.mortbay.log - started ErrorHandler@5c8c5c8c 10:52:53.232 [Start Help Server] DEBUG org.mortbay.log - started org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet-1917940305 10:52:53.232 [Start Help Server] DEBUG org.mortbay.log - started org.mortbay.jetty.servlet.Context@7e0f7e0f{/help,null} 10:52:53.233 [Start Help Server] DEBUG org.mortbay.log - starting Server@7d537d53 10:52:53.244 [Start Help Server] DEBUG org.mortbay.log - started org.mortbay.jetty.nio.SelectChannelConnector$1@4b764b76 10:52:53.245 [Start Help Server] INFO org.mortbay.log - Started SelectChannelConnector@0.0.0.0:51041 10:52:53.245 [Start Help Server] DEBUG org.mortbay.log - started SelectChannelConnector@0.0.0.0:51041 10:52:53.245 [Start Help Server] DEBUG org.mortbay.log - started Server@7d537d53
Believe it or not it's normal for a web server to be started when you hover in a java editor. I'm wondering if this is normal logging and it's just appearing because we have added a certain logging package. This is just tracing info and doesn't seem to indicate a problem.
(In reply to comment #1) > I'm wondering if this is normal logging and it's just appearing because we have > added a certain logging package. Maybe this is it, because the same steps don't cause a problem in 3.6 PW
IMHO the logging itself is the bug. I just found my console flooded with similar messages when opening the help browser (using 3.6 RC4). Has some component accidentally hard-coded full debug output? Is there at least an option to turn of all this noise?
(In reply to comment #3) > IMHO the logging itself is the bug. Sorry, yes, this bug was a complaint about logging to the console, not that the jetty server started up. PW
It seems we have some SLF4J bundles installed in 4.0 builds, but I can't see where they are coming from.
If you use Help>Help Contents, jetty will log every click while you navigate the help. I20100727-1520 PW
I am getting this output on the 3.x I20100824-1210. Where should we send this bug to? UA?
(In reply to comment #7) > I am getting this output on the 3.x I20100824-1210. Where should we send this > bug to? UA? Dani? Chris?
Using 3.6 or the latest 3.7 build you would not see these messages in the log. It looks as though some debug settings are turned on which are causing this output from Jetty. I'm not sure how Jetty debug settings are turned on and off, maybe Simon has an idea.
(In reply to comment #9) > Using 3.6 or the latest 3.7 build you would not see these messages in the log. I got the logging messages with I20100824-1210 which is pretty recent. Was the bug fixed in the last week or so? What is the number?
I just tried Eclipse 3.7 build I20100824-1210 ( on Win XP ), I launched a new workspace, created a plug-in project and hovered over class names until the help system started up but did not see any messages written to the console. I don't know why I'm not seeing the same problem. It would help if we knew what test Jetty performed when deciding whether to turn on debug messages.
>Dani? Chris? Rather UA but I've never seen this so far.
Moving to UA. Chris, should we try to find someone from Jetty to comment on this?
David has reported something similar in bug 324922.
FWIW, the default SLF4J/Logback configuration is *full* debug logging to console and that's likely what happening here. Everybody that gets the console log message is likely running with SLF4J + Logback bundles. There are multiple options available. 1. Point to default log configuration which disables logging. This can be done via a system property pointing to a log config file. It might also be possible to provide a default config via a fragment. 2. Upgrade to SLF4J >= 1.6 to avoid the dependency on Logback. Since 1.6.0 SLF4J is able to run without a logging implementation. It will just emit a single warning upon start up and discard all logging afterwards. 3. Don't install SLF4J at all. That might only be possible if no other bundle is importing SLF4J api. The Jetty bundle in Orbit is capable of running without SLF4J.
*** This bug has been marked as a duplicate of bug 324922 ***
