Skip to main content
  • EN

Hi,

 

I am using an FME Server app in which a theHTTPCaller is used to call on a second FME Server workspace. Here are some of the tags used in the URL (opt_showresult=true&opt_servicemode=sync&opt_responseformat=json)

Long translations fail and return a HTTP 504 (HTTP/1.1 504 Gateway Time-out) even with the connection timeout lenght and transfer timeout lenght set to 0

 

Is there a way to avoid these timeouts? I suspect that it has to do with the FME Cloud settings, anybody can shed some light on the subject?

 

Cheers,

Itay

I don't have an answer for you but can confirm that this sometimes seems to happen on FME Cloud instances, up to the point where even the standard dashboard statistics gathering job times out.

I don't have an answer for you but can confirm that this sometimes seems to happen on FME Cloud instances, up to the point where even the standard dashboard statistics gathering job times out.

Hi thanaks for confirming I am not the only one having an issue with it this. I probably should configure the proces to submit an async jobs to avoid the time-out.

Are you passing your calls to FME Server through IIS?

Are you passing your calls to FME Server through IIS?

Hi, No this is pure FME Cloud.

Out of curiosity, how long is the duration before you get the timeout error?

I am also curios about this topic. It would be nice to have an option for a diverted page when gateway times out.

 

I have had this happen only when the file uploaded is too large, typically files more than 100mb and the processing time in the workspace that I have times out. Can one limit the file size uploaded to the FME Cloud?

@rag2000​ - If you see a gateway time-out HTTP 504 error, your issue might not be that the file upload is too big, but that the job takes too long to run. We have some custom logic to increase the timeout on certain endpoints (/fmerest/v3/transformations/transact/jobs and /fmerest/v3/transformations/transact/data) to mitigate this issue.

@rag2000​ - If you see a gateway time-out HTTP 504 error, your issue might not be that the file upload is too big, but that the job takes too long to run. We have some custom logic to increase the timeout on certain endpoints (/fmerest/v3/transformations/transact/jobs and /fmerest/v3/transformations/transact/data) to mitigate this issue.

Hi @Merline George​ 

Thanks for getting back to me on this issue. I have had a look at the endpoints and according the documentation: "The submittal is synchronous, and a response is not returned until the job completes"

 

Does that mean that the Server app will also wait until the responce is returned? or will it time-out?

Reply


Community Stats

30,099
Posts
114,258
Replies
37,729
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.