Question

Why does my job start another instance of the same job after 5 minutes?

F

Hi,

My workspace is reading data from excel and uploading it to gis database. Data streaming is used to be able to return an html to the user.

 

My implementation works if it's run natively from the fme application, but when it's uploaded to the server it will start a duplicate of the same job after 5 minutes. Both of these jobs will then run from start to finish, meaning that duplicates will be created.

It seems that this happens only when the excel file has atleast 330 rows. I have also checked that engine does not crash.

 

4 replies

merlinegeorge
Rank
Badge +5

Hello,

 

Would you be able to provide the Job logs for the two successful runs?

Is this the only workspace affected?

Is this on a schedule or automation?

hkingsbury
Rank
Userlevel 5
Badge +29

Are you triggering the job through the FMEREST API? Could it be that the front end is expecting a call within 5 minutes and if it doesn't get a response, try it again?

Check out the Abley FME Firesides on Youtube: https://www.youtube.com/@ableyltd
F

This is the only workspace affected and this workspace is just ran through the workspace app link (.../fmeserver/apps/name). It is always starting the duplicate exactly after 5 minutes. I inspected the network requests and it is pending all the way until the duplicate is finished.

 

Unfortunately I am not able to share the job logs.

But here is explained what is happening during one minute before the duplicate starts:

 

  • Reading data from different tables of our database with FeatureReader
  • 64 rows marked in the log with the same exact second (52 seconds before dup), most of them marked as "STATS"
    • coordinatesystemsetter, Vertex creator, reprojector, coordinaterounder
    • Testers
    • ListBuilder
    • AttributeManager
    • AttributeFilter
    • Sorter
    • Excel Reader: Closing dataset?
    • FME API version of module 'ArcSDE' matches current internal version
    • Performing query against ArcSDE dataset
    • Connection made to server X for dataset Y
  • Then for the rest of the minute FeatureReader is reading table/feature class and continues reading after the duplicate is created.
  • (And ofc there is not mention anywhere indicating that new workspace would be started)
F

So far I've compared line by line the logs when the workspace is ran locally vs the workspace ran from fme server and there and there seems to not be anything out of ordinary.

I've also tried to increase the time for some fmeServerConfig.txt settings, with no results (it still starts a duplicate exactly at 5 minutes):

RELAYER_MAX_PUBLISHER_ACCEPT_ATTEMPTS=30000 -> 33000

CONNECTIONPOOL_EXPIRY=300 -> 330

SOCKET_HANDSHAKE_TIMEOUT=30000 -> 33000

 

Reply


Community Stats

28,670
Posts
109,366
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.