将 AsyncPostBackTimeout 设置为较大值(300 秒)是否存在潜在问题?
是否有任何理由不设置 ScriptManager.AsyncPostBackTimeout 到一个(相对)较大的值,例如 5 分钟?
我有一个报告需要 30 到 180 秒才能运行,这会导致 Sys.WebForms.PageRequestManagerTimeoutException:服务器请求超时。
错误。
在我所有的搜索中,我找不到大超时的缺点,但我想知道是否有人有实践经验,并且可以证明将其增加到远高于默认的 90 秒是否安全?
Are there any reasons to not set the ScriptManager.AsyncPostBackTimeout to a (comparitively) large value like 5 minutes?
I have a report that takes anywhere from 30 to 180 seconds to run, which causes a Sys.WebForms.PageRequestManagerTimeoutException: The server request timed out.
error.
In all my searching I can't find a downside of a large timeout, but I'm wondering if anyone has hands-on experience and can attest to whether it's safe to increase it well above the default 90 seconds?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我已经在一个应用程序上运行这个程序超过 8 个月了,该应用程序每小时获得适量的异步回发 (<1000),并且将
AsyncPostBackTimeout
设置为 300 时没有遇到任何问题秒。我可以想象,如果一直存在极长时间运行的请求的可能性,它会产生问题,但目前看起来完全稳定。I've been running this for over 8 months on an application that gets a moderate number of asynchronous postbacks per hour (<1000), and I haven't run into any problems with
AsyncPostBackTimeout
set to 300 seconds. I can imagine it creating problems if there are possibilities of extremely long running requests happening all the time, but it seems completely stable currently.