Question

Timeout error running multiple WFS readers.

  • 26 April 2022
  • 5 replies
  • 24 views
e.steven

I have a workbench set up with multiple WFS readers, default parameters. It will run 1 reader and complete its process. When moving to the next WFS reader it will throw a timeout error:

 

[2]: HTTP transfer error: Timeout was reached

[2]: Please ensure that your network connection is properly set up

[2]: No proxy settings have been entered. If you require a proxy to access external URLs, please ensure the appropriate information has been entered

<WFS> Timeout was reached- Unable to fetch the capabilities document:

 

If I disable readers and run each individually they all work. Any ideas what I'm doing wrong?

5 replies

rahulsharma
Rank
Badge +8

Hi @e.steven​ 

I have not encountered this behavior before, is it possible to share the WFS URLs (if they are public).

Workaround

Try using Chained Feature Readers (one after another) to access multiple servers.

 

e.steven

Hi @e.steven​ 

I have not encountered this behavior before, is it possible to share the WFS URLs (if they are public).

Workaround

Try using Chained Feature Readers (one after another) to access multiple servers.

 

Hi There, thanks a lot for responding. Here are three of the open ones (roads/railways/address points). Whichever reader is first will run fine and output, it just throws the error on the second read.

 

https://data.linz.govt.nz/services;key=872022e255f7407b9e6438c4112af59b/wfs/layer-53382?service=WFS&request=GetCapabilities

https://data.linz.govt.nz/services;key=872022e255f7407b9e6438c4112af59b/wfs/layer-50319?service=WFS&request=GetCapabilities

https://data.linz.govt.nz/services;key=872022e255f7407b9e6438c4112af59b/wfs/layer-53382?service=WFS&request=GetCapabilities

 

I am simply processing some attributes and outputting them to a local SDE as they form the basis of some in house services. The aim is the bench will be scheduled monthly on FME server once working. Thanks again.

 

 

e.steven

I have now narrowed this issue down to the use of the Feature Writer transformer or a gdb writer. When using a shape file output for each WFS this issue does not occur.

rahulsharma
Rank
Badge +8

I have now narrowed this issue down to the use of the Feature Writer transformer or a gdb writer. When using a shape file output for each WFS this issue does not occur.

That is very strange, Do you mind sharing your workspace?

I tried with the above dataset using the Esri Geodatabase (File Geodb) writer and was able to write the data without any problems

e.steven

This issue was solved eventually. Due to PAC configurations on my organisations network. As a temp solution proxy settings were changed in FME options to circumvent.

Reply


Community Stats

28,666
Posts
109,343
Replies
36,535
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.