I believe it can be when you are using Feature Inspection mode (run with Full Inspection). When it hits a breakpoint the processes are suspended. Of course, that might not be the only occasion. FME hitting a memory or license limit and so temporarily stopping are other thoughts - but only guesses on my part.

Is it causing an issue or a slowdown? Do they ever start up again?

---

I believe it can be when you are using Feature Inspection mode (run with Full Inspection). When it hits a breakpoint the processes are suspended. Of course, that might not be the only occasion. FME hitting a memory or license limit and so temporarily stopping are other thoughts - but only guesses on my part.

Is it causing an issue or a slowdown? Do they ever start up again?

Not using feature inspection mode.

 

The processes hangs for until killed, ie they never start up again.

 

 

There should be enough memory. If I run the childworkspace independently it only has a peak process memory usage of 236500 kB.

 

 

---

Inappropriate behaviour in the FME workplace, sorry 'Workspace'...

---

Not using feature inspection mode.

 

The processes hangs for until killed, ie they never start up again.

 

 

There should be enough memory. If I run the childworkspace independently it only has a peak process memory usage of 236500 kB.

 

 

Well, I looked this up and found a few cases that showed the issue. There's not a consistent reason why the problems occurred - in some cases it seemed to fix itself (sometimes after a reinstall) and in other cases either the user was doing something wrong (writing to an invalid location) or the system itself was sick.

 

One item that was more definite: WorkspaceRunner was using the wrong FME (multiple versions were installed). So check the logs to make sure it is running the right FME for each child.

 

Otherwise I think the only way to sort it out is to send us a copy of your workspaces, and log files too, and see what we can figure out.

 

---