Symptoms

All of the engines are running large jobs and you have published a large workspace to the FME Server. The FME Server logs start reporting that no engines are running:

>Warning: No FME Engines are available to this FME Server. You can submit jobs,>however they cannot be processed in this state. Ensure your FME Engines are>licensed, check that the machines on which these FME Engines reside are>running, and then restart FME Server if required.

However, if you open a process explorer on the server, it reports both engines are still running. No new Jobs will start until the FME Server is restarted.

Cause

The reason for the crash is that the FME Server Core ran out of Java heap memory when parsing the large Workspace you tried to upload.

Resolution

On the Server Core the max JVM heap memory for FME Server 2011 and lower is 128MB. If you change the max JVM heap memory to 512MB then Server Core should handle it. In FME 2012 and higher the default max JVM heap memory is set to 512MB.

  1. Open the <FME Server Install Dir>\Server\processMonitorConfig.txt file.
  2. Change the max JVM heap memory by changing -Xmx128m to -Xmx512m in the following block of text:
CMDFMEServer_Core="C:/Apps/FMEServer//Utilities/jre/bin/FMEServer.exe"-FMESERVER_CLASSPATH"C:/Apps/FMEServer//Server/lib/*;C:/Apps/FMEServer//Server/lib/fmeutil/fmeutil.jar;C:/Apps/FMEServer//Utilities/jdbc/*"-Djava.library.path="C:/Apps/FMEServer//Server/lib/fmeutil"-Djava.security.manager-Djava.security.policy="C:/Apps/FMEServer//Server/security/fmeserver.policy"-Djava.security.auth.login.config="C:/Apps/FMEServer//Server/security/fmeserver.config"-Xms32m -Xmx512m -Xrs COM.safe.fmeserver.FMEServer"C:/Apps/FMEServer//Server/fmeServerConfig.txt" -MONITOR_PORT 0|attempts=20