Question

Strange freeing memory limits in job log

  • 26 October 2022
  • 3 replies
  • 4 views
M

Hello,

 

We are experiencing strange memory limits messages in job log:

 

2022-10-26 16:31:36 | System Status: 20.00 GB of physical memory available

2022-10-26 16:31:36 | System Status: 30.00 GB of virtual memory available

2022-10-26 16:31:37 | FME Configuration: Start freeing memory when the process exceeds 60.00 GB

2022-10-26 16:31:37 | FME Configuration: Stop freeing memory when the process is below 45.00 GB

 

How are these limits calculated, because start and stop freeing memory limits are greater in size than the available physical/virtual memory?

 

3 replies

M
Badge +2

@miro.vrbanic​ The messages are explained here

M

Thank you @Mark Stoakes​.

We checked that article before, it explains general settings and messages about memory management.

 

We have a situation that during job log "just stops" and job fails because engine crashes (restarts).

In fmeprocessmonitorengine.log there is no "memory related" messages, just the general:

Fri-04-Nov-2022 08:40:42.657 PM  WARN   Engine1  393562 : Process "Engine1" ended unexpectedly. Being restarted on attempt 1...

 

On Windows server running the FME Core/Engine we monitored memory usage using PerfMon and in the moment of engine crash, there was 1.8 GB of physical memory available.

 

That's why we suspect that the FME calculated the freeing memory limits in a bad way, and in reality never started the optimizing process.

 

We are running:

FME Server 2021.2.4

Build 21814 - win64

M
Badge +2

Thank you @Mark Stoakes​.

We checked that article before, it explains general settings and messages about memory management.

 

We have a situation that during job log "just stops" and job fails because engine crashes (restarts).

In fmeprocessmonitorengine.log there is no "memory related" messages, just the general:

Fri-04-Nov-2022 08:40:42.657 PM  WARN   Engine1  393562 : Process "Engine1" ended unexpectedly. Being restarted on attempt 1...

 

On Windows server running the FME Core/Engine we monitored memory usage using PerfMon and in the moment of engine crash, there was 1.8 GB of physical memory available.

 

That's why we suspect that the FME calculated the freeing memory limits in a bad way, and in reality never started the optimizing process.

 

We are running:

FME Server 2021.2.4

Build 21814 - win64

@miro.vrbanic​ This is likely an FME engine crash - probably not related to memory. What does the job log say? If there is no error in the job log then it's very likely an FME crash. Try testing the workspace on FME Desktop. If that also crashed then with an error in the workbench log "Error running translation" then you'll need to start disabling parts of your workspace until you find the offending part

Reply


Community Stats

28,698
Posts
109,448
Replies
36,548
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.