系统崩溃并返回，因此只需更改 web.config
我有一个叫BOS的系统。当 3、4、5 或更多浏览系统时，系统会崩溃。
解决办法是进入web.config，编辑它（任何修改，甚至可能是空格）并再次保存。瞧，系统返回了。
我的问题是这个？ 可能的原因有哪些？ 这可能与什么有关？代码还是基础设施？ 怎么解决？
I have a system called BOS. The system crashes when 3, 4, 5 or more browsing the system.
The solution is to go into web.config, edit it (any modification, it may even be a blank space) and save it again. And voila, the system returns.
My question is this?
What are the possible causes that?
What may be related to this? Code or Infrastructure?
How to solve?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
它可能仅设置为处理大约 5 个同时请求，并且此时它会变得无响应。如果是这种情况，请尝试进入您的 IIS 设置并进行更改，尽管提供的信息很少，但确实很难说。你所说的崩溃是什么意思？ Internet Explorer 崩溃？ IIS 崩溃？系统变得无响应并且新请求超时？
It's possible that it is only set up to handle around 5 simultaneous requests and it just becomes unresponsive at that point. Try going into your IIS settings and changing that if this is the case, although it's really hard to say with so little information provided. What do you mean by crashes? Internet Explorer crashes? IIS crashes? System just becomes unresponsive and new requests time out?
我会在 IIS 的“性能”选项卡下查看。您可能指定了最大连接阈值或带宽阈值。每次修改 web.config 文件时，它都会重新启动应用程序，这就是它再次开始工作的原因。
如果这不起作用，我可能会看看 ANTS Performance Profiler 或 ANTS Memory Profiler 之类的东西。它将有助于识别导致系统崩溃的任何瓶颈。它可能是任何东西，但分析工具可能有助于缩小罪魁祸首的范围。
I would look under the Performance tab in IIS. You might have a maximum connection threshold or bandwidth threshold specified. Every time you modify the web.config file it restarts the application, which is why it starts working again.
If that doesn't work, I would maybe look at something like ANTS Performance Profiler or ANTS Memory Profiler. It will help to identify any bottlenecks that are causing your system to crash. It could be anything, but profiling tools might help to narrow down the culprits.