Skip to main content
Question

Workspace runner dillema - different results

  • January 24, 2020
  • 3 replies
  • 28 views
salvaleonrp
Enthusiast
Forum|alt.badge.img+20

Whenever I run my child workspace by itself I get correct results on my translation written to a SQL Server table.

If I run this workspace from its parent workspace I lose attributes coming from a specific output stream going into a featuremerger with multiple suppliers..

Top picture is result from child workspace; bottom is if child is ran from a runner. At the bottom I lost values to HTTP response success, FeatureLayerCount and Selected Features.

These 3 attributes come from junction 6d: Workflow stats.

I added a Feature holder before featuremerger hoping that can solve the issue but it did not.

Seeking ideas or anyone who have similar experiences with workspacerunner.

Thanks!

 

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.

3 replies

ev_robin
Contributor
Forum|alt.badge.img+12
  • ev_robinContributor
  • Contributor
  • January 24, 2020

Do you have the option "Wait for job to complete" checked in your WorkspaceRunner transformer?

salvaleonrp
Enthusiast
Forum|alt.badge.img+20
  • salvaleonrpEnthusiast
  • Author
  • Enthusiast
  • January 24, 2020

Do you have the option "Wait for job to complete" checked in your WorkspaceRunner transformer?

It is set yo Yes. The thing about using workspacerunner is you don't have a visual of what's happening with the child workspace until the translation is finished and you open the log file. perhaps I should compare the two translation logs and see where it's deviating.

salvaleonrp
Enthusiast
Forum|alt.badge.img+20
  • salvaleonrpEnthusiast
  • Author
  • Enthusiast
  • January 24, 2020

Looking at the logs of two successful runs of the same child workspace and just searching for Junction_15 where the dropped attributes are coming from, this is how they compare.

Examining the second log file at 56.5 seconds I found out the root of the problem.

Is there a way to optimize memory before I run the parent? I understand two FME.exe are simultaneously running so that's an instant memory overhead. An option is to stay in one workbench file and run my second workspace from the shutdown script with python.

 

Community Stats

32,182
Posts
122,179
Replies
39,856
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.