Skip to main content
  • EN

Hello!

I recently upgraded to the new FME 2019.0 (yay!).

This has had an interesting side-effect for running workspaces using the workspaceRunner for me. I have the following setup (I simplified the names for ease of explanation):

  • Workspace 1 runs periodically and checks for changes in a dataset
  • It pushes the changes to workspace 2 using the workspaceRunner
  • Workspace 2 receives a change, and it dynamically starts all workbenches within a folder (let's say 3 and 4)
  • Workspace 2 starts workspace 3 and 4 using the SystemCaller, as it's near-impossible to use the workspaceRunner with a dynamic path AND parameters
  • Workspaces 3 and/or 4 start and do their work

In 2018.1 this worked fine, but since upgrading this setup has started spawning command line screens whenever a change occurs. This is royally annoying as it moves the focus from the screen I was working on, to these screens. They look like this:

(These screens show the output for running FME from the command line).

This only happens when, inside the WorkspaceRunner, the "Wait for Job to Complete" is set to "No". If it's set to "Yes", it doesn't happen.

Side note: if I set the setting to "Yes", I have all sort of timeouts from our MSSQL database. No clue why.

To me this looks like a bug. An obscure one, I'll admit, but still :-)

Does anyone else have this problem? Is there a fix for this?

 

Thank you in advance.

 

Best regards,

 

Pijke

I think you should consider contacting Safe support directly on this one. I'm sure it would be very helpful if you could include your workspaces as well as the complete logs from one of the runs.

Hi @pijke, Can I request to send us your sample workspaces to understand the workflow. But initial investigation does conclude that there is a changed behavior from 2018 to 2019.

 

Please submit a support ticket https://www.safe.com/support/report-a-problem/ along with your workspaces ( we do not require data itself), the one that uses SystemCaller and how its configured.

Hi @pijke, Can I request to send us your sample workspaces to understand the workflow. But initial investigation does conclude that there is a changed behavior from 2018 to 2019.

 

Please submit a support ticket https://www.safe.com/support/report-a-problem/ along with your workspaces ( we do not require data itself), the one that uses SystemCaller and how its configured.

Hi @rahulsharma,

A couple of weeks ago I submitted a support case, but haven't heard back yet. If you want, I can PM you the case reference number.

Best regards,

 

Pijke

Hi @pijke, Yes there are 2 Cases and I see the one is waiting on your response (C143855) is that correct one?

Hi @pijke, Yes there are 2 Cases and I see the one is waiting on your response (C143855) is that correct one?

Yes, that is the correct one.

Reply


Community Stats

30,159
Posts
114,480
Replies
37,806
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.