ASP.NET Web API.控制器未命中.完全没有回应.诊断方法? [英] ASP.NET Web Api. Controller not hit. No response at all. Approaches to diagnose?

查看:100
本文介绍了ASP.NET Web API.控制器未命中.完全没有回应.诊断方法?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个以前可以使用的控制器方法,目前尚不清楚什么更改(如果有的话)导致了以下问题:

I have a controller method which was previously working and it's not clear what change, if any, has caused the following problem:

未命中控制器.毫无例外,没有响应,没有状态码,甚至没有来自服务器的任何响应(在Fiddler中检查).该请求最终超时.

The controller is not hit. There is no exception, no response, no status code or indeed any response from the server (checked in Fiddler). The request eventually times out.

更新

请在下面查看我的答案.另请参阅我的后续问题:

See my answer below. Also see my follow up question:

网络API控制器方法执行到结束.没有HTTP响应.挂起

推荐答案

这个问题似乎是实际问题的产物.似乎是浏览器/中间件/网络应用正在对请求进行排队,而先前挂起的请求导致所描述的行为最终被注意到是正在等待可用的套接字...")

This problem appears to be an artefact of the actual problem; which appears to be that the browser/middleware/web-app are queuing the requests and previous hung requests are causing the behaviour described eventually noticed to be 'waiting for available socket...')

在无尘室中发生的情况略有不同(控制器方法执行到最后并返回结果,但是没有HTTP响应),并提出了一个新问题,请参见

What happens in a clean room situation is slightly different (the controller method executes to the end and returns a result, however there is no HTTP response) and warrants a new question, see Web API Controller method executes to end. No HTTP response. Hangs

这篇关于ASP.NET Web API.控制器未命中.完全没有回应.诊断方法?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆