Bugzilla – Full Text Bug Listing
| Summary: | Galileo help.eclipse.org is down with error 503 | ||
|---|---|---|---|
| Product: | Community | Reporter: | Martin Oberhuber <mober.at+eclipse> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | Keywords: | helpwanted |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://help.eclipse.org/galileo/index.jsp | ||
| Whiteboard: | |||
| Bug Depends on: | 310809 | ||
| Bug Blocks: | |||
|
Description
Martin Oberhuber
It would be great if it stopped crashing... This is Eclipse running on a server; someone here should be able to help out? The last time it was restarted was May 31, so it lasted all of seven days before crashing. As I mentioned on bug 310809, I think you need to increase mem to for instance -vmargs -Xmx512m -XX:MaxPermSize=256m especially when the search index is being generated. Also, what version of Eclipse is serving here? I would suggest upgrading to 3.6RC4. (In reply to comment #2) > As I mentioned on bug 310809, I think you need to increase mem to for instance > -vmargs -Xmx512m -XX:MaxPermSize=256m > especially when the search index is being generated. I'm not sure where to put those arguments... Here is the command line that is used to start the help server: /usr/bin/java \ -classpath /home/data/httpd/help.eclipse.org/galileo/eclipse/plugins/org.eclipse.help.base_3.4.0.v200906111540.jar \ org.eclipse.help.standalone.Infocenter -clean -command start \ -eclipsehome /home/data/httpd/help.eclipse.org/galileo/eclipse -port 8087 \ -nl en -locales en \ -plugincustomization /home/data/httpd/help.eclipse.org/galileo/eclipse/plugin_customization.ini & > Also, what version of Eclipse is serving here? I would suggest upgrading to > 3.6RC4. We run the Infocenter from the actual release... the Ganymede infocenter is being run on the Ganymede version, Galileo on Galileo, etc. (In reply to comment #3) Assuming that you are using a Sun JVM, here are the args I suggest: -Xmx256m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError The first two actually match the Galileo default settings from eclipse.ini - which are not taken into account when you launch your Infocenter directly with "java", so you end up with Sun's default max heap size which is pretty small. The 3rd argument is in order to generate a heap dump in case your infocenter should run out of memory. You'll then know for sure that the problem was caused by an OOME and you need to increase your mem sizes. Developers can also use the http://www.eclipse.org/mat in order to analyze the heap dump and understand who's been the memory pig. > I'm not sure where to put those arguments... Here is the command line Put the args just after "/usr/bin/java". Running off Galileo is fine, of course. In case you are using an IBM JVM, you'll need slightly different arguments. I would suggest just keeping the 1st one, removing the 2nd one, and consulting this document for the 3rd one... but I'm not an expert on IBM JVM's: http://wiki.eclipse.org/index.php/MemoryAnalyzer#IBM_Java_5.0_and_Java_6_Virtual_Machine_dump_options Thanks, Martin. We're using the IBM JVM, but those parameters seem to have worked. I've added them to Galileo, and also to the new Helios infocenter. The infocenters seem to be much more stable with the memory settings. Thanks for the hint, Martin. |