Windows 2008 R2 SP1 64位中的愚蠢窗口综合症缓解中的错误？ [英] Bug in Silly Window Syndrome Mitigation in Windows 2008 R2 SP1 64 bit?

问题描述

以前是否有人见过这个？ 我有一个运行在Windows Server 2008 R2 SP1 64位上的.NET 2.0应用程序（下面的"！ - 客户端"），它正在调用挂起的外部Web服务（下面的"webservices"）。 似乎愚蠢的
窗口综合症预防正在发挥作用 - 即服务器将数据发送回客户端的速度超过它可以处理的速度 - 因此客户要求它减速。 然而，在1297帧中有一个奇怪的36秒间隔。 我们在TCP窗口数据包中看到这些巨大的
跳转，此时，服务器停止响应。

Has anybody seen this before?  I have a .NET 2.0 application ("!-client" below) running on Windows Server 2008 R2 SP1 64-bit that is calling an external webservice ("webservices" below) that hangs.  It appears that the Silly Window Syndrome prevention is kicking in - i.e. the server is sending back data to the client faster than it can process it - so the client asks it to slow down.  However, there's a bizarre 36 second interval in frame 1297.  We see these huge jumps in the TCP window packets and at that point, the server stops responding.

奇怪的是，当我们运行客户端时，我们看不到这一点一个32位的应用程序。 当我们在它工作时跟踪它时，我们看不到这些大间隔，因为它会打开TCP窗口备份。 另外，我们在亚马逊，Azure和本地机器上运行这个
因此它与客户端的位置无关。 也许是Windows Server 2008 R2 SP1傻窗口综合症预防中的一个错误？

Stranger still, we don't see this when we run the client as a 32-bit application.  When we trace it when it works, we don't see these big intervals as it opens the TCP Window back up.  In addition, we've run this on Amazon, Azure and local machines so it's not related to where the client is.  Maybe a bug in Windows Server 2008 R2 SP1 Silly Window Syndrome prevention?

任何想法都将不胜感激！

Any ideas would be greatly appreciated!

跟踪片段截图（TCP疑难解答）列）：

Screenshot of trace snippet (TCP Troubleshooting columns):

推荐答案

你好Rob

我看起来像应用程序！ - 客户端不能耗尽tcp缓冲区（！-client在＃972,981,1012中发送0的RWIN）直到＃1297（现在是RWIN 3472）。那时我希望websrv能够再次开始发送数据但不会。 ！-Clients等待5分钟为
数据然后放弃（FIN在＃2711）。

I looks to me like the application on !-client cannot drain the tcp buffer (!-client sends RWIN of 0 in #972,981, 1012) until #1297 (now RWIN 3472). At that point I would expect websrv to start sending data again but doesn't. !-Clients waits 5 minutes for data then gives up (FIN in #2711).

我可能会看看为什么应用程序需要36秒才能耗尽tcp缓冲区接下来。

I would probably look at why the application is taking 36 seconds to the drain the tcp buffer next.

-Wes

这篇关于Windows 2008 R2 SP1 64位中的愚蠢窗口综合症缓解中的错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！