Question

httpCaller timeout when multiple features and API 204 and has no content as responce

R

Hi,

 

I'm trying to use a HTTPCaller with multiple features but when the API has no response (no content) with the OK code 204, HTTPCaller give me back a timeout. It is like its is expecting anything otherwise, HTTPCaller returns timeout. On the API endpoints with OK return (200) there is no problem, but when calling the API with no content as return, this problem happens.

 

I could bypass this problem with a Decelerator with 1 second per feature (less than 1 sec same error occurs), but I don't thing this is the most appropriate way to do it so.

 

Any Ideas?

Thanks

4 replies

R

Just an addition to it: In the DB, the API made the changes correctly

R

HTTPCaller return messages (error):

_error: Timeout was reached

fme_rejection_code: NO_RESULT

response_body: 300D0A0D0A485454502F312E3120323034204E6F20436F6E74656E740D0A5472616E736665722D456E636F64696E673A206368756E6B65640D0A5365727665723A204D6963726F736F66742D4949532F31302E300D0A582D506F77657265642D42793A204153502E4E45540D0A446174653A205765642C203034204D617220323032302031383A32343A353320474D540D0A0D0A300D0A0D0A

------------

HTTPCaller return messages (OK):

http_status_code: 204

response_body:

 

 

nathanatsafe
Rank
Badge +7

Hi @rodrigoaires,

 

 

Thanks for your post. We ran your question by our development team, but I think we need more information before we can accurately assess what's causing this behaviour, and how FME should handle it. Would you please open a support ticket here and include your workspace as well as a log file of your translation with log debug mode turned on? https://www.safe.com/support/report-a-problem/ You can find log debug mode in FME Options:

 

In a rare case it's possible that, if the server also sends a content-length header along with the 204 response, the HTTPCaller might time out while waiting for the content to arrive (which it never will).

 

 

Best,

 

Nathan
R

Hi @nathanatsafe

ticket opened!

One more thing... the end point URL is different for each feature.

feature 1:

URL: http://myAPI.com/products/garden/areas

body: [{"name":"flower"}]

feature 2:

URL: http://myAPI.com/products/appliance/areas

body: [{"name":"stove"}]

 

FME httpCaller sits and waits for a response of the API until it timeout

Reply


Community Stats

28,661
Posts
109,324
Replies
36,528
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.