Skip to main content
Question

Zombie fme.exe after using WorkspaceRunner

  • February 16, 2019
  • 4 replies
  • 33 views
W
Forum|alt.badge.img

Hello,

 

Today I wanted to experiment a bit. I used WorkspaceRunner with "wait for end" option set to no.

 

 

It worked quite well for some time, I had few hundreds of featured to be processed using this, but after some time it all slowed down and then stopped.

 

Then I stopped job in fme workbench and tried to run it again. There was information that I dont have enough licenses.

I saw that problem before so I thought that it would be enough only to open task manager end kill some fme.exe processes but there were none.

 

Then I opened powershell and entered get-process command

 

Here there are.

 

When I try to kill any of those processes it doesnt work, still list is the same

 

Do you know that problem? I hope that there are better ways for solving that then computer reboot :)

 

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

redgeographics
Celebrity
Forum|alt.badge.img+59
  • redgeographicsCelebrity
  • Celebrity
  • 3697 replies
  • February 17, 2019
The WorkspaceRunner fires off the child workspace once for every feature you run through it and if you don't set it to wait for completion it potentially has 7 child workspaces running at the same time. I think if you manually kill the master workspace (i.e. the one with the WorkspaceRunner) and then immediately start it again the child processes are potentially still running. They should, however, run to completion and then shut down.
FME rocks! \m/
W
Forum|alt.badge.img
  • witos
  • Author
  • 45 replies
  • February 17, 2019
The WorkspaceRunner fires off the child workspace once for every feature you run through it and if you don't set it to wait for completion it potentially has 7 child workspaces running at the same time. I think if you manually kill the master workspace (i.e. the one with the WorkspaceRunner) and then immediately start it again the child processes are potentially still running. They should, however, run to completion and then shut down.

Hello @redgeographics

Thank you for reply. The problem is that main workspace was manualny terminated and right now I can't kill those child processes like I described im the question. They don't use any resources and already've been there for 20 hours. I can't kill those processes using task manager or cmd or powershell. The only way to terminate them that I know is to reboot machine but maybe you know different way?

redgeographics
Celebrity
Forum|alt.badge.img+59
  • redgeographicsCelebrity
  • Celebrity
  • 3697 replies
  • February 17, 2019

Hello @redgeographics

Thank you for reply. The problem is that main workspace was manualny terminated and right now I can't kill those child processes like I described im the question. They don't use any resources and already've been there for 20 hours. I can't kill those processes using task manager or cmd or powershell. The only way to terminate them that I know is to reboot machine but maybe you know different way?

A reboot would probably sort that out but if this happens again you may want to get in touch with Safe's support. Killing the master workspace should also terminate the child workspaces when they're done.
FME rocks! \m/
ebygomm
Influencer
Forum|alt.badge.img+44
  • ebygommInfluencer
  • Influencer
  • 3422 replies
  • February 18, 2019

Hello @redgeographics

Thank you for reply. The problem is that main workspace was manualny terminated and right now I can't kill those child processes like I described im the question. They don't use any resources and already've been there for 20 hours. I can't kill those processes using task manager or cmd or powershell. The only way to terminate them that I know is to reboot machine but maybe you know different way?

It seems strange that you cannot kill them via task manager. I can terminate child workspaces this way with no issues (normally when I've had to kill the parent workspace, after realising I've left redirect to inspector on!)

Community Stats

32,058
Posts
121,723
Replies
39,686
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.