Opened 51 years ago
Last modified 10 years ago
#887 new defect
IZ560: JVM refuses to start with message "Fork of jvm executor_vm failed: {1}"
Reported by: | easymf | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | hedeby | Version: | 1.0 |
Severity: | Keywords: | Sun bootstrap | |
Cc: |
Description
[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=560]
Issue #: 560 Platform: Sun Reporter: easymf (easymf) Component: hedeby OS: All Subcomponent: bootstrap Version: 1.0 CC: None defined Status: NEW Priority: P4 Resolution: Issue type: DEFECT Target milestone: 1.0u5next Assigned to: adoerr (adoerr) QA Contact: adoerr URL: * Summary: JVM refuses to start with message "Fork of jvm executor_vm failed: {1}" Status whiteboard: Attachments: Issue 560 blocks: Votes for issue 560: Vote for this issue Opened: Wed Aug 13 03:51:00 -0700 2008 ------------------------ Description: If system installation is corrupted (for example, logging.properties is missing in system spool directory), JVM refuses to start (expected behavior) but the message is corrupted, giving not-proper details about the real problem. The corrupted message looks like: Fork of jvm JVM_NAME failed: {1} where "JVM_NAME" is a jvm identifier. Evaluation: The problem is of lower priority, as it does not affect the functionality of the system. It is just annoying, as user has limited information why the jvm refuses to start. Suggested Fix / Work Around: The workaround (to get better information what is wrong) is to start sdmadm command with "-d" global option: "sdmadm -d suj -j JVM_NAME". Fix has to correct the messages that should contain the real cause of the problem. Analysis: Problem is caused by missing parameters to GrmException in com.sun.grid.grm.boostrap.ParentStartupService class on lines 169, 296, 302. The constructor has to contain additional parameter, "ex.getLocalizedMessage()". How to test: Testsuite test has to be created, that will perform following: 1. corrupt an installation of hedeby on a selected host by removing "logging.properties" from spool directory. 2. starting an executor_vm on that host (assuming that executor_vm is setup on that host). 3. check that error message from "sdmadm suj" is not "Fork of jvm executor_vm failed: {1}", but "Fork of jvm executor_vm failed: File: "<hedeby_spool>/logging.properties" does not exist" where <hedeby_spool> is local hedeby spool dir on the selected host. ETC: 0.5 PD for the fix 1.0 PD for the test ATC: ------- Additional comments from adoerr Wed Aug 20 07:43:55 -0700 2008 ------- New target milestone. ------- Additional comments from torsten Fri Nov 27 00:40:09 -0700 2009 ------- changed milestone to 1.0u5next
Note: See
TracTickets for help on using
tickets.