Client ConnectionFailure：在转发请求时 [英] Client ConnectionFailure: at forward-request

问题描述

Hello Team，

Hello Team,

表格最近几天收到错误"ClientConnectionFailure：at forward-request"在API管理网关中。根据来自后端服务的日志，我发现花了8.3分钟（所以我认为它可能会更慢）和通过API管理调用此API
的客户端（exe）可能已经设置了超时。

Form last few days am getting error "ClientConnectionFailure: at forward-request" in API management gateway . As per logs from backend service i see that it took 8.3 mins ( so i believe it might be slower ) and client ( exe) who calls this API through API management might have set time out .

如果有人可以分享下面的见解

could be great if someone can share the insights for below

1，可能会很棒。 API管理中API的默认超时时间是什么？

1. what is the default time out for API in API management ?

2。如果API管理的超时设置为3秒而后端服务需要2分钟才能执行，会发生什么？我们上面会例外吗？幕后实际发生的事情， 这个触发操作会被取消到后端api吗？

2. what will happen if time out at API management is set to 3s and backend service takes 2 mins to execute ? will we above exception ? what actually happen behind the scenes ,  will this trigger operation cancelled to back end api ?

3。如果我们有客户端将时间设置为5秒而Azure API有2分钟而后端服务有2分钟会发生什么？我们会得到同样的例外吗？ azure API管理是否考虑根据其策略设置的时间或由客户设置？ 

3. what will happen if we have client who sets the time out to 5s and Azure API has 2min and backend service has 2min ? will we get the same exception ? Does azure API management consider the time out set at it's policies or set by the client ? 

4。我知道我们不应该花费那么多时间的API，但鉴于它是一种遗产，我们必须在生产中花费一些时间，应该为此做些什么？我们是否应该增加API管理的时间，我们是否应该向客户提出
？

4. I know that we should not have API taking that much time but given the fact that it is kind of legacy and we have to live with some time in production , what should be done for this ? Should we increase the time out for API management and should we ask our client also ?

任何输入都非常受欢迎

问候，

Rajesh

推荐答案

嗨Rajesh - 看看
此主题可回答您的一些问题，即：默认超时为无限。



我认为微调超时是你可以采取的克服这个问题的方法之一，特别是如果你的后端需要长达8分钟。但是，通过阅读您的问题，听起来现在是开始使用
的好时机
缓存策略？也就是说，如果您的后端响应内容在一段时间内保持静态，就像您在文档中找到的那样。



b $ b

Hi Rajesh - Have a look at this thread for answers to some of your questions, i.e: default timeout is infinite.

I think that fine-tuning timeouts is one of the approaches you can take to overcome this issue, especially if your backend is taking as long as 8mins. However, reading through your questions, it sounds like it's now a good time to start using caching policies? That is, of course, if your backend response content remains static over a period of time, as you'd find in the documentation.

这篇关于Client ConnectionFailure：在转发请求时的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！