Question

How to get the Job ID from a failing FMEServerJobSubmitter?

  • 8 February 2017
  • 9 replies
  • 8 views
erik_jan
Rank
Userlevel 2
Badge +12

Using FME Server and Desktop 2016.1 I created a workspace calling a job on FME Server using the FMEServerJobSubmitter transformer.

The "Wait for server job to complete" is set to "Yes".

If the job succeeds I use the _job_id to get the log file and email using the file as attachment.

If the job fails (it generated a log file containing an error) I do not get the _job_id attribute (see image).

How can I retrieve the log file from the server if the job fails, but produces a log file?

This log file is even more urgent than the succeeded job's log file.

9 replies

itay
Rank
Badge +16

Hoi @erik_jan,

You can use the REST API to query the falied jobs filter the one you are looking for and with the help of the job id,retrieve the job's logfile.

see the REST API documentation:

https://docs.safe.com/fme/html/FME_REST/v2/apidoc/index.html#!/transformations/list_get_11

https://docs.safe.com/fme/html/FME_REST/v2/apidoc/index.html#!/transformations/log_get_8

hope this helps.

erik_jan
Rank
Userlevel 2
Badge +12

Hoi @erik_jan,

You can use the REST API to query the falied jobs filter the one you are looking for and with the help of the job id,retrieve the job's logfile.

see the REST API documentation:

https://docs.safe.com/fme/html/FME_REST/v2/apidoc/index.html#!/transformations/list_get_11

https://docs.safe.com/fme/html/FME_REST/v2/apidoc/index.html#!/transformations/log_get_8

hope this helps.

But don't you need the job id to check the status of the job?

 

I would expect the job id to be an output attribute (same as on succeeded jobs).

 

 

david_r
Rank
Userlevel 4

It is my experience that the FMEServerJobSubmitter in 2016 is buggy in this respect. As an example, the FMEServerJobSubmitter returns a different set of attributes depending on whether the master workspace is executed on Desktop and Server.

You might want to verify if that is the case for you, in my quick test it seems the FMEServerJobSubmitter does indeed return a _job_id attribute but 1) it is not automatically exposed in the workspace and 2) it is only available then the master workspace is running on Server, not on Desktop.

I think this has been improved in FME 2017, at least the _job_id attribute is now readily available on the <Rejected> port.

If nothing else works and you can't upgrade to 2017, you might want to consider using the REST API through the HTTPCaller rather than the FMEServerJobSubmitter to execute your child workspace, at least then you're guaranteed to get a job id.

erik_jan
Rank
Userlevel 2
Badge +12

It is my experience that the FMEServerJobSubmitter in 2016 is buggy in this respect. As an example, the FMEServerJobSubmitter returns a different set of attributes depending on whether the master workspace is executed on Desktop and Server.

You might want to verify if that is the case for you, in my quick test it seems the FMEServerJobSubmitter does indeed return a _job_id attribute but 1) it is not automatically exposed in the workspace and 2) it is only available then the master workspace is running on Server, not on Desktop.

I think this has been improved in FME 2017, at least the _job_id attribute is now readily available on the <Rejected> port.

If nothing else works and you can't upgrade to 2017, you might want to consider using the REST API through the HTTPCaller rather than the FMEServerJobSubmitter to execute your child workspace, at least then you're guaranteed to get a job id.

Thanks @david_r. I will try the AttributeExposer and let you know the results.

 

itay
Rank
Badge +16
But don't you need the job id to check the status of the job?

 

I would expect the job id to be an output attribute (same as on succeeded jobs).

 

 

Not with the the section command that will result in all the jobs and their id's then it's a question of issueing a second command to retrieve the log file
itay
Rank
Badge +16
But don't you need the job id to check the status of the job?

 

I would expect the job id to be an output attribute (same as on succeeded jobs).

 

 

@erik_jan, just make sure you set the detail level to high ( when using v2 of the api) to get the ws name as part of the response.

 

 

http://yourserver/fmerest/v2/transformations/jobs/completed?detail=high&limit;=-1&offset;=-1

 

 

 

erik_jan
Rank
Userlevel 2
Badge +12

It is my experience that the FMEServerJobSubmitter in 2016 is buggy in this respect. As an example, the FMEServerJobSubmitter returns a different set of attributes depending on whether the master workspace is executed on Desktop and Server.

You might want to verify if that is the case for you, in my quick test it seems the FMEServerJobSubmitter does indeed return a _job_id attribute but 1) it is not automatically exposed in the workspace and 2) it is only available then the master workspace is running on Server, not on Desktop.

I think this has been improved in FME 2017, at least the _job_id attribute is now readily available on the <Rejected> port.

If nothing else works and you can't upgrade to 2017, you might want to consider using the REST API through the HTTPCaller rather than the FMEServerJobSubmitter to execute your child workspace, at least then you're guaranteed to get a job id.

@david_r This seems to be working. Thanks again.

 

T

 

How do I fix this error?

david_r
Rank
Userlevel 4

 

How do I fix this error?

I may be due to a problem that occurs before FME even gets to initialize the job log (e.g. startup scripts, etc). Have a look at the FME Server system logs and search for errors there.

 

Reply


Community Stats

28,669
Posts
109,357
Replies
36,531
Members
Terms & ConditionsCookie 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.