Suddenly the Foglight Management Server (FMS) stops and it is not possible to restart it. In the log files no obvious error can be found. During the crash, the FMS creates a hs_err_pidxxx.log file with this content:
---
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000000140027423, pid=708, tid=4312
#
# JRE version: 6.0_24-b07
# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C [fms.exe+0x27423]
[...]
Stack: [0x0000000028050000,0x0000000028150000], sp=0x000000002814e520, free space=1017k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [fms.exe+0x27423]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
[...]
---
Bug in the FMS 5.6.4.2 on Windows platforms:
The code which is failing, is custom native code which is used to spawn child processes (such as those driven from command actions). The native code in question was added mainly to support starting external processes on Solaris.
WORKAROUND:
Add the following start up parameter into the server.config file:
server.vm.option0 = "-Dquest.common.process-runner.disabled=true";
(If server.vm.option0 is already in use, select server.vm.option1 or server.vm.option2, ....)
STATUS: COM-1282 has been raised and is currently scheduled to be fixed in 5.7.1 release of Foglight Management Server (FMS).
