Question

AreaAmalgamator FME 2019 possible bug?

Forum|Forum|6 years ago
September 16, 2019
6 replies
31 views

northswejohan

Hi,

The AreaAmalgamator does not seem to work in FME2019, when I use the same data and workspace in FME2017 it works fine. Even when there is no data passing the AreaAmalgamator it makes the workspace crash, when I use a dummy polygon input to the AreaAmalgamator in the same workspace it works. I have this problem on Workbench and Server 2019.

Thanks for any help:)

Best/

Johan

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.

+61

redgeographics
Celebrity
Forum|Forum|6 years ago
September 16, 2019

Can you share a sample workspace/data (which is causing the crash) here? Which build number are you using?

FME rocks! \m/

Upvote

+11

jovitaatsafe
Safer
Forum|Forum|6 years ago
September 20, 2019

Hi @northswejohan,

Definitely interested in this one! Would you be able to provide a sample workspace/data as @redgeographics had suggested? A full log file would also be useful to get your build number so we can give it a try on our end and see if it's an issue that we need to file for our development team to look over. Thanks!

- Jovita

Upvote

olivier
Contributor
Forum|Forum|5 years ago
November 29, 2019

We recently migrated to FME 2019.2 and discovered that the AreaAmalgamator was causing the workspace translation to crash when receiving no data to consume. This has been reported to Safe Software support team and was filed with number FMEENGINE-62317. This issue has an impact on our operations. Hopefully it will be resolved soon. The proposed workaround is to put the AreaAmalgamator in a child workspace and call it with a WorkspaceRunner...

Upvote

+11

jovitaatsafe
Safer
Forum|Forum|5 years ago
November 29, 2019

Thanks @olivier for sharing the PR number and workaround! I've linked this Q&A to the issue reported and we'll post here again when the issue has been addressed. You'll also be notified of any resolution through your case emails.