Microsoft KB Archive/829054

= FIX: A COM+ server load may not balance across all servers when Component Load Balancing first loads =

Article ID: 829054

Article Last Modified on 11/8/2004

-

APPLIES TO

 Microsoft COM+ 1.0, when used with:  Microsoft Windows 2000 Standard Edition

 Microsoft Windows 2000 Datacenter Server 

-





SYMPTOMS
On a computer that is running Microsoft Windows 2000 Advanced Server, when you try to load Microsoft COM+ components that are deployed in Microsoft Application Center 2000 Component Load Balancing (CLB), the load may not be balanced as expected.



CAUSE
This issue occurs if two COM+ components try to load at the same time. Both COM+ components have an equal chance of becoming the load balancing activator. The threads of the components experience a race condition when they try to create the load balancing activator object at the same time.

When thread A initializes the object, thread B uses the load balancing activator object that is being initialized by thread A. This condition prevents thread B from obtaining the correct load balancing activator.

Because thread B is accessing the load balancing activator object while thread A is initializing it, the returned object is not a load balancing activator object. Therefore, the object that is returned to thread B does not activate against the remote server. Instead, the object that is returned to thread B activates on the local computer (DLLHost).



How to obtain the hotfix
This issue is fixed in the Windows 2000 Server COM+ 1.0 Hotfix Package 28. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

828748 FIX: Availability of Windows 2000 Post-Service Pack 4 COM+ 1.0 Hotfix Rollup Package 28

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.

Keywords: kbqfe kbfix kbbug kbwin2000presp5fix KB829054

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.