为什么页面发布需要这么长时间？
我在某些页面回发方面遇到一些问题，需要很长时间才能执行。 如果我执行“appcmd list requests”，我可以得到如下信息：
REQUEST "79000001800004e3" (url:POST /dir/file.aspx, time:87219 msec, client:xxx.xxx.xxx.xxx, stage:ExecuteRequestHandler, module:ManagedPipelineHandler) REQUEST "8600000080002f82" (url:POST /dir/file.aspx, time:61391 msec, client:xxx.xxx.xxx.xxx, stage:AcquireRequestState, module:Session) REQUEST "5e00010280000420" (url:POST /dir/file.aspx, time:21047 msec, client:xxx.xxx.xxx.xxx, stage:AcquireRequestState, module:Session)
这是一个导致问题的特定文件（在本例中为 dir/file.aspx）。它来自同一个 IP 地址。第一个来自 ManagedPipelineHandler 模块，后两个来自 Session 模块。
我没有关于网络浏览器的任何详细信息，也没有关于客户端的更多信息。
我查了一下sql死锁，没有找到。根本没有长时间运行的 SQL 查询。
您知道可能出现什么问题吗？
问候。
I am having some problems with some page post backs that take a loooong time to execute.
If I do a "appcmd list requests" I can get something like this:
REQUEST "79000001800004e3" (url:POST /dir/file.aspx, time:87219 msec, client:xxx.xxx.xxx.xxx, stage:ExecuteRequestHandler, module:ManagedPipelineHandler) REQUEST "8600000080002f82" (url:POST /dir/file.aspx, time:61391 msec, client:xxx.xxx.xxx.xxx, stage:AcquireRequestState, module:Session) REQUEST "5e00010280000420" (url:POST /dir/file.aspx, time:21047 msec, client:xxx.xxx.xxx.xxx, stage:AcquireRequestState, module:Session)
It's one particular file that causes the problem (dir/file.aspx in this case). It comes from the same IP-adress. And the first on is from ManagedPipelineHandler module and the two after that from Session module.
I do not have any details about the web browser, or anything more about the client for that matter.
I have looked for sql dead locks and did not find any. There are no long running sql queries at all.
Do you have any idea of what can be the problem?
Regards.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
目前，问题似乎是由于服务器上启用了快速故障保护造成的。当抛出太多异常时，应用程序会重新启动，这需要相当长的时间，并且在此期间请求会被放入队列中。
Currently, it looks like the problem was due to the fact that Rapid Fail Protection was enabled on the server. When too many exceptions were thrown the application restarted, which takes quite a time to do, and during that time the requests were put on queue.