Skip to main content
Question

Parallell processing - licensing issues

  • September 30, 2016
  • 6 replies
  • 6 views
sigtill
Supporter
Forum|alt.badge.img+24

I seem to be getting the same issue as described here: http://gis.stackexchange.com/questions/22427/fme-error-failed-to-validate-fme-worker-licence-key

After the same amount of time I get "Failed to validate FME worker licence key" - after approx processing 1 000 000 objects. I need parallell processing due to the size of the data, I have tried Aggressive only, and also Extreme.

Below is a screenshot showing part of the process. The Parallell runs in Parallell (:)).

After approx 1hour 20 minutes the logfile fills with "Failed to validate FME worker licence key" and the fmeworker.exe gets stuck with no work done (0.01 percent CPU constantly).

I use FME 2016.1 - floating license - Oracle Edition.

Also tried on FME 2017 - same issue

@Mark2AtSafe

The real SigTill

6 replies

sigtill
Supporter
Forum|alt.badge.img+24
  • sigtillSupporter
  • Author
  • Supporter
  • September 30, 2016
Also tried it on FME 2017 - same issue.

 

 

The real SigTill
sigtill
Supporter
Forum|alt.badge.img+24
  • sigtillSupporter
  • Author
  • Supporter
  • September 30, 2016

It seems when they are run in Parallell the Parallell 2 try to start before all processes of Parallell 1 is finished. Putting a FeatureHolder after FeatireWRiter 2 and directting the summary from FeatureWriter2Holder to Parallell 1 seems to solve the issue so that there is a license free when Parallell starts the second time.

So the issue is that if one Parallell Processing custom transformer is only finished with X-1/X processes when the second Parallell Processing custom transformer tries to start 1/X processes it crashes. It seems all of the processes of a Parallell Processing custom transformers needs to be complete and done before a second Parallell Processing transformer can try to start even a single process.

This can be solved by making sure a featuerholder is used somewhere between the 2 Parallell Processing transformers

The real SigTill
sigtill
Supporter
Forum|alt.badge.img+24
  • sigtillSupporter
  • Author
  • Supporter
  • October 4, 2016
I have now filed C120198 for this, attached logfile, workspace and screenshot. I have made sure the Parallell is run after each other by using a FeatureHolder inbetween. So everything is "free" before a new Parallell runs.
The real SigTill
martinkoch
Supporter
Forum|alt.badge.img+18
  • martinkochSupporter
  • Supporter
  • February 22, 2018

Has the issue been resolved yet in a newer version of FME? I have exactly the same problem using build 16494 - WIN64. I tried searching for PR#43805 and C120198 but I keep finding only this post.

I use parrallel processing in writing to an Oracle database. All works fine on a fast FME machine with a fast licence-server and a slow connection to Oracle. On a slow machine with a fast Oracle connection it fails after about this 1 hour and 20 minutes.

mark2atsafe
Safer
Forum|alt.badge.img+44
  • mark2atsafeSafer
  • Safer
  • February 22, 2018
martinkoch wrote:

Has the issue been resolved yet in a newer version of FME? I have exactly the same problem using build 16494 - WIN64. I tried searching for PR#43805 and C120198 but I keep finding only this post.

I use parrallel processing in writing to an Oracle database. All works fine on a fast FME machine with a fast licence-server and a slow connection to Oracle. On a slow machine with a fast Oracle connection it fails after about this 1 hour and 20 minutes.

That PR number is marked as closed-fixed. It was back-ported to a newer version of FME2016 - build 16709 (2016.1.3 branch) - so if you give that a try I am hopeful it will work. If not, please do let us know.

 

martinkoch
Supporter
Forum|alt.badge.img+18
  • martinkochSupporter
  • Supporter
  • February 26, 2018
martinkoch wrote:

Has the issue been resolved yet in a newer version of FME? I have exactly the same problem using build 16494 - WIN64. I tried searching for PR#43805 and C120198 but I keep finding only this post.

I use parrallel processing in writing to an Oracle database. All works fine on a fast FME machine with a fast licence-server and a slow connection to Oracle. On a slow machine with a fast Oracle connection it fails after about this 1 hour and 20 minutes.

Thanks Mark. Unforunately I am stuck at the current build due to the update policy at this client. Waiting for 2018.1 for this one...

 

 

Reply


Helpful Members This Week

Community Stats

31,222
Posts
118,394
Replies
38,822
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.