Low Memory Conditions Cause Server to Fail New Connections This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article was previously published under Q188284 SYMPTOMS
If a low memory condition occurs during a replication, Content Deployment
may fail to accept new connections.
CAUSE
Under low-memory situations, the _beginthread call can fail as the thread
pool is expanded. The internal counter tracking the number of threads in
the thread pool is increased even though the call fails. When the thread
pool is later decreased to 1 (using the internal counter, which no longer
reselects the actual number of active threads), there will be no active
threads, and all incoming connections will fail.
RESOLUTION
In this condition, the thread pool will never grow. Therefore, the only way
to recover is to stop and restart the service.
To resolve this problem, apply the next Site Server 3.0 service pack when it becomes available. STATUS
Microsoft has confirmed this to be a problem in Site Server version 3.0.
This problem was corrected in the latest Microsoft Site Server version 3.0
U.S. Service Pack. For information on obtaining the service pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
