Community
Participate
Working Groups
Any attempt to load the navigation pane seems to instead just generate an OOME. HTTP ERROR 500 Problem accessing /help/index.jsp. Reason: INTERNAL_SERVER_ERROR Caused by: java.lang.OutOfMemoryError at java.util.zip.ZipEntry.initFields(Native Method) at java.util.zip.ZipEntry.<init>(ZipEntry.java:117) at java.util.zip.ZipFile$3.nextElement(ZipFile.java:488) at java.util.zip.ZipFile$3.nextElement(ZipFile.java:466) at org.eclipse.osgi.baseadaptor.bundlefile.ZipBundleFile.getEntryPaths(ZipBundleFile.java:276) at org.eclipse.osgi.baseadaptor.BaseData.getEntryPaths(BaseData.java:124) at org.eclipse.osgi.framework.internal.core.AbstractBundle.findLocalEntryPaths(AbstractBundle.java:1454) at org.eclipse.osgi.framework.internal.core.AbstractBundle.findEntries(AbstractBundle.java:1393) at org.eclipse.equinox.jsp.jasper.JspServlet$ServletContextAdaptor.getResource(JspServlet.java:172) at org.apache.jasper.JspCompilationContext.getResource(JspCompilationContext.java:274) at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:362) at org.apache.jasper.compiler.Compiler.isOutDated(Compiler.java:332) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:560) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:303) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.equinox.jsp.jasper.JspServlet.service(JspServlet.java:112) 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:76) 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:326) 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)
I've restarted the help service. -M.
It's down again. You should consider increasing VM Size as per bug 310809 comment 2 and maybe enabling a heap dump to analyze what's taking up all the memory...
Here's the current startup options: -Xmx1024m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError If you'd like to help decipher the 110M heap file I'm more than willing to send a copy along. In the mean time I've restarted the help service. -M.
When a server app struggles to serve static web pages with 1G of RAM allocated to it, that has to be a bug, right? Should we move this to platform/ua?
Yep, that's just what I was about to suggest ... clone a bug into platform UA that it takes too much mem. ZIP and upload your heap dump to a place where it's accessible. Using Eclipse Memory Analyzer (MAT) it should be pretty straightforward to see what's taking up all the mem ... download the http://eclipse.org/mat/ RCP, then load the heapdump, within 10 minutes you should have a first impression.
I tried to use MAT to open the heap dump but it throws the following: Error opening heap dump 'heapdump.20110809.080814.31640.0008.phd'. Check the error log for further details. Not a HPROF heap dump (java.io.IOException) Not a HPROF heap dump I'll clone this bug and attach the dump. -M.
