I send many features into HTTPFetcher, before that, I have used Decelerator to slow down the speed of request. But if one request couldn't get response, FME will wait it all the time.
How solve this? Thanks
Hi,
Page 1 / 1
Hi,
one possible solution: After the HTTPFetcher, check the "Status code variable" and "Error attribute" values supplied by the HTTPFetcher.
If they indicate an error (timeout), use a VariableSetter to indicate an error. Before the HTTPFetcher, insert a VariableRetriever and a Tester to stop sending features to it if the error variable has been set.
David
Thanks David,
If one feature cann't get the response, what ever how long it past, FME just keeps waiting. features remained won't be passed untill it get the result.
So what I need is just the timeout setting and let the workflow keeps going.
Hi,
I'm not quite sure I understand. Does the HTTPFetcher hang indefinitely when there is not response? It should stop with a timeout exception after some time.
On Windows, there is a system-wide timeout setting, usually between 30-60 seconds, which I believe FME uses. Take a look at the Microsoft Knowledge Base article here to locate and modify this setting.
David
Hi,
Yes, but just one time I waited for 20 minutes and FME keeps hanging, beside that, not more than 1 minute.
I wish I can set it to 5 seconds.
Thank you
Hi,
look again at the article I linked to. I shows you how to find your current timeout value, as well as how to modify it.
David
Hi,
I tried your method and set it to 10 seconds (value 10000), but it doesn't work. FME hang indefinitely again.
Thanks
I check the option Follow Redirects and it works !
Thanks JulienM,
Now I cann't reproduce the problem, I'll try your method next time.