Known Issue: FME Server Automation fails to trigger job after Automation Writer

Liz Sanderson
Liz Sanderson
  • Updated


Known Issue ID FMESERVER-15954
Discovered 2020
Affects All Versions
Resolved 2022.0


In my Automation, I have two Run Workspace actions, the second is meant to be triggered by a feature output by an Automations Writer in the first workspace. This feature is very large and the second workspace fails to submit. There is no evidence in the Automation Log that the translation request was ever received.

Other troubleshooting steps you may have taken:

  • If I swap the Run Workspace out for a Log Action, I can see the workspace is completing successfully and the Automation Writer is passing out this feature. 
  • If I reduce the size of the feature parsed out of my Automation Writer the job will submit successfully.



By default the subscriber_workspace protocol is allocated a max heap memory of 256MB, this protocol is crashing because the request is exceeding this size, this can be seen in the fmeprocessmonitorcore.log in Resources > Core > Current: 

INFORM     Subscriber_workspace   Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
WARN     Subscriber_workspace   393562 : Process "Subscriber_workspace" ended unexpectedly. Being restarted on attempt 1...
WARN     Subscriber_workspace   393563 : 

 1) Review the log file for the job that was running when the problem occurred.
 2) Check that the terminated program is not already running on the system.
 3) Check that correct license(s) are in effect.



We recommend you adapt your workflow to reduce the output of the Automation Writer. One suggestion is to write the contents out to a file in your first workspace and parse the file path only to the Automation Writer which can then be read in your second workspace. Alternatively, you can increase the memory allocated to this protocol by following the instructions below to modify one of FME Server's configuration files.

  1. Run a text editor as administrator and open processMonitorConfigCore.txt located in <FMEServerInstallDir>\Server\

  2. Find the section: 

    # Start FME Server Subscriber Plugin (workspace)
    START_SYSTEM_Subscriber_workspace="C:/Program Files/FMEServer/Utilities/jre/bin/FMESubscriber.exe" -FMESERVER_CLASSPATH "C:/Program Files/FMEServer/Server/lib/*;C:/Program Files/FMEServer/Server/lib/fmeutil/*;C:/Program Files/FMEServer/Utilities/jdbc/*" -Xms32m -Xmx256m "C:/Program Files/FMEServer/Server/config/subscribers/"
  3. Update -Xms32m -Xmx256m to -Xms32m -Xmx1024m and save the file. This will update the max heap size to 1GB but FME will only use this much if it is needed. 

  4. Restart FME Server to apply this change.

Was this article helpful?



Please sign in to leave a comment.