Community
Participate
Working Groups
Sorry, I have absolutely no idea as to what product/component I should raise this bug against. I was hoping to find jetty in equinox but ... well feel free to reassign if Equinox/Framework isn't the accurate target. When opening the Eclipse Help (through Help => Help Contents) and navigating to multiple documentations, we always end up with IOExceptions filling the error log. That can happen on the very first opened doc as it can happen with the 5th so pretty random... but I have always reproduced it within the first 10 docs containing images I opened. Once one of these exceptions has been thrown, nearly all subsequent documents we open will throw it again; effectively filling the error log with noise. Note that this only happen with documentation containing images (or at least I haven't reproduced it with anything else). The exception message ([1] and [2]) changes according to what failed to load ... but the stack trace [3] is always the same. Note that this can be reproduced with both 3.6RC3 and 3.6RC4, I haven't given a try to any previous build. [1] Error processing help request org.eclipse.wst.xsl.doc/html/images/launching/XSLRunDebugConfigurations.png [2] Error processing help request org.eclipse.wst.xsl.doc/html/images/editor/syntaxColoring.png [3] org.mortbay.jetty.EofException at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:789) at org.mortbay.jetty.HttpConnection.flushResponse(HttpConnection.java:693) at org.mortbay.jetty.HttpConnection$Output.close(HttpConnection.java:993) at org.eclipse.help.internal.webapp.servlet.EclipseConnector.transfer(EclipseConnector.java:191) at org.eclipse.help.internal.webapp.servlet.ContentServlet.doGet(ContentServlet.java:45) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:322) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:924) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) Caused by: java.io.IOException: Une connexion existante a dû être fermée par l’hôte distant at sun.nio.ch.SocketDispatcher.writev0(Native Method) at sun.nio.ch.SocketDispatcher.writev(Unknown Source) at sun.nio.ch.IOUtil.write(Unknown Source) at sun.nio.ch.SocketChannelImpl.write0(Unknown Source) at sun.nio.ch.SocketChannelImpl.write(Unknown Source) at java.nio.channels.SocketChannel.write(Unknown Source) at org.mortbay.io.nio.ChannelEndPoint.flush(ChannelEndPoint.java:232) at org.mortbay.io.nio.SelectChannelEndPoint.flush(SelectChannelEndPoint.java:211) at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:712) ... 25 more
Moving to User Assistance for now, although it looks like this may be some jetty error. I could not reproduce with the Eclipse SDK help on the Mac. And we have lots of documents with images that I loaded. Do you have to go through the documents fast or the speed of switching documents does not seem to have any relationship with the ability to reproduce? Also does the number of images on the page seem to matter?
I went through the docs quickly as I myself was trying to reproduce the bug a colleague reported to me. Also note that this has been reproduced on both the modeling package and a "classic" download with wtp installed; not a "clean" Eclipse. Also, A colleague cannot reproduce this on linux, and the two computers on which we observed this bug were running Windows 7. I'll try and reproduce this while running slowly through the docs, leaving each ends its loading before switching to a new one, but for now assume this is due to me asking for a new documentation too fast.
Going slowly enough to let the pages finish their loading seem to minimize the issue ... but it doesn't prevent it either. I can't find a page that allow for 100% reproduction for this issue :/. However I did observe the failure on more than the images : Error processing help request org.eclipse.platform.doc.user/book.css Error processing help request org.eclipse.php.help/html/whmsg.js The stack trace remains the same.
This is the same problem that was reported in Bug 314324. I have yet to isolate it to a small test case but I have not yet tried doing reads in parallel, that may be the key. I've only seen it happen on files which get pulled in by html or xhtml files such as .css, .js files or images. I am continuing to look into the problem. *** This bug has been marked as a duplicate of bug 314324 ***
Thanks for the pointer to the duplicate, and good luck :).
