Skip to main content
Archived

FME Server Job Logs: Indicate when the job was resubmitted due to FME Engine cra

Related products:FME Flow
  • April 20, 2017
  • 3 replies
  • 32 views

fmelizard
Safer
Forum|alt.badge.img+21

***Note from Migration:***

Original Title was: FME Server Job Logs: Indicate when the job was resubmitted due to FME Engine crash


When a translation crashes an FME Engine, it is resubmitted up to (the default) three times before it is reported as failed. There is no indication in the resultant Job log that it had been resubmitted - this would be very useful information in case further investigation into the cause is needed.

3 replies

Forum|alt.badge.img
  • April 21, 2017

Crashing without telling is bad. It makes something that's probably critically important (a workspace crashing is rarely good!) invisible to those maintaining the system.

If a workspace crashed the first 1 or 2 times but then worked next time, currently the end-user/sys-admin would never know there was a problem.

Thinking about it, in the case of a crash, by default an email (to server-admin?) should probably be sent. If the crash is only indicated via the web interface on the job summary (and it should be there too), that's going to be almost as invisible as currently, especially for workspaces that are not triggered via the web interface.


Forum|alt.badge.img

A line in the log of the resubmitted job with the failed job id and / or a line added to the failed job log with the new job id, or put it in the request / result data, respectively.


LizAtSafe
Safer
Forum|alt.badge.img+18
  • Safer
  • April 5, 2025
OpenArchived