Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 299833 - Last Review: September 26, 2005 - Revision: 1.2
FIX: A COM+ Server Polling Failure May Block CLB for Entire Cluster
This article was previously published under Q299833
On This Page
SYMPTOMS
If a COM+ server that is using Component Load Balancing (CLB) fails to respond to CLB polling, new instantiation requests on components that are configured for dynamic load balancing and that are destined for failed COM+ servers may block until DCOM times out. Furthermore, in high-stress environments, all new instantiation requests may eventually block. This behavior may persist for about 20 seconds. After this delay, CLB resumes normal operation.
NOTE: When a COM+ server that is using CLB fails to respond to CLB polling, existing instantiations of components on that server block until DCOM times out and may not recover.
CAUSE
When a COM+ server that is using CLB fails to respond to CLB polling, the CLB polling thread waits for the response and is unable to update the routing list of COM+ servers. This results in a static routing list of COM+ servers. New instantiation requests on components that are configured for dynamic load balancing "round robin" through the routing list, which includes the failed COM+ server or servers. Each new instantiation request that is destined for a failed COM+ server blocks a thread until DCOM times out on the COM+ routing server or servers. In high-stress environments, this behavior may eventually consume all available threads on the COM+ routing server or servers, resulting in a failure to load balance COM+ components. This condition lasts until the blocked CLB polling thread times out and updates the CLB routing list (approximately 20 seconds). After the CLB routing list is updated, CLB resumes normal operation with all new instantiation requests routed to the remaining active COM+ servers.
RESOLUTION
To resolve this problem, upgrade to Application Center 2000 Service Pack (SP) 1. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
309384Â
(http://kbalertz.com/Feedback.aspx?kbNumber=309384/EN-US/
)
INFO: How to Obtain the Latest Application Center 2000 Service Pack
STATUS
Microsoft has confirmed that this is a bug in Application Center 2000.
This bug was corrected in Application Center 2000 Service Pack 1.
MORE INFORMATION
Fixed Behavior
If a COM+ server that is using CLB fails to respond to CLB polling, existing instantiations of components that are configured for dynamic load balancing may stop responding (hang) and may not recover unless the COM+ server that experienced the failure recovers.
If a COM+ server that is using CLB fails to respond to CLB polling, it is dropped from the routing list at the end of the next polling interval and new instantiation requests are routed to the remaining active COM+ servers.
APPLIES TO
- Microsoft Application Center 2000 Standard Edition
| kbhotfixserver kbqfe kbbug kbfix KB299833 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please