Skip to main content
Question

FME Server 2016.1 Job using an extra FME License when using FMEJobSubmitter

  • March 6, 2018
  • 3 replies
  • 12 views
A

Currently, we noticed that the scheduled job in FME Server is consuming an extra FME license. This happens when the FME Script contains an FMEJobSubmitter. We can see that another fme.exe process is available in the Windows Task Manager aside from the other 4 allotted for the FME Engines.

This should not happen.

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

david_r
Celebrity
  • david_rCelebrity
  • 8391 replies
  • March 6, 2018

I think the only reliable way to check for the number of licenses used by FME Server is the "Engine & Licensing" page, not the Windows task manager. What does the engine page look like when this occurs -- could you post a screenshot here?

That said, there were some issues similar to these in FME Server 2017 which apparently have been fixed in 2018. I'm not sure if those issues were present in 2016.1, however, you'll have to ask Safe support for more info.

A
  • azajarc
  • Author
  • 7 replies
  • March 7, 2018

I think the only reliable way to check for the number of licenses used by FME Server is the "Engine & Licensing" page, not the Windows task manager. What does the engine page look like when this occurs -- could you post a screenshot here?

That said, there were some issues similar to these in FME Server 2017 which apparently have been fixed in 2018. I'm not sure if those issues were present in 2016.1, however, you'll have to ask Safe support for more info.

My colleague and I have tested this. A new fme.exe appeared once we start a scheduled job that contains the FMEJobSubmitter. He's looking at the Licensing and he can see the account that was added to the license list. After he killed the running job (via the windows task manager), the license was released. We were able to replicate this as well by starting another job with FMEJobSubmitter.

 

Thanks, I'll ask Safe support for more info.

 

 

david_r
Celebrity
  • david_rCelebrity
  • 8391 replies
  • March 7, 2018
My colleague and I have tested this. A new fme.exe appeared once we start a scheduled job that contains the FMEJobSubmitter. He's looking at the Licensing and he can see the account that was added to the license list. After he killed the running job (via the windows task manager), the license was released. We were able to replicate this as well by starting another job with FMEJobSubmitter.

 

Thanks, I'll ask Safe support for more info.

 

 

Ask them about case number C119862 (and possibly also C121974) to see if it's related.

Community Stats

32,060
Posts
121,724
Replies
39,688
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.