Skip to main content
Question

FMEServerJobSubmitter Job not queued

  • February 1, 2017
  • 3 replies
  • 8 views
erik_jan
Contributor
Forum|alt.badge.img+26

Using FME Desktop and Server 2016.1, I created a workspace that uses FMEServerJobSubmitters to start a series of jobs on the FME Server, all depending on the previous job.

This process works as designed, even with just 1 engine.

But if another process has claimed the engine, the workspace fails with the error that no license is available.

I would have expected my job to go to the queue.

Has anybody else experienced this behavior of the job submitted via FMEServerJobSubmitter?

If so, can this be avoided in any way?

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

erik_jan
Contributor
Forum|alt.badge.img+26
  • erik_janContributor
  • Author
  • Contributor
  • February 3, 2017
@aaronkoning @stewartharper Any idea from the FME Server team?
sigtill
Supporter
Forum|alt.badge.img+25
  • sigtillSupporter
  • Supporter
  • February 3, 2017

Have you had any "hard fail jobs" ? Try to restart FME Server - and then run the workspace again. Sometimes an engine gets "stuck". I have experienced this.

The real SigTill
erik_jan
Contributor
Forum|alt.badge.img+26
  • erik_janContributor
  • Author
  • Contributor
  • February 3, 2017

Have you had any "hard fail jobs" ? Try to restart FME Server - and then run the workspace again. Sometimes an engine gets "stuck". I have experienced this.

Thanks for the reply @sigtill. We restarted the server and that solved the issue, because the engine became available.

 

But next time somebody else claimed the engine before this process starts running it will be the same.

 

My issue is that I expected it to be queued if the engine is not available, instead of returning an error.

 

Community Stats

32,207
Posts
122,301
Replies
39,891
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.