Microsoft Knowledge Base Email Alertz

KBAlertz.com: (820448) - After a COM+ application server stops responding, some Component Load Balancing (CLB) clients may not respond for about 40 seconds.

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 820448 - Last Review: May 30, 2003 - Revision: 1.3

PRB: CLB Clients May Be Slow to Respond After a COM+ Application Server Stops Responding

SYMPTOMS

After a COM+ application server stops responding, some Component Load Balancing (CLB) clients may not respond for about 40 seconds.

CAUSE

CLB detects a COM+ application server that is not responding when CLB polls for response times (by default, every 800milliseconds). If any COM+ component activation request comes in after the server stops responding and before the next CLB poll, the CLB routers continue to send object activation requests to the unresponsive server. The COM+ client thread waits until DCOM times out (by default, after about 40 seconds) before the object creation request is considered unsuccessful and the thread continues. Depending on the client program design, this may make the application appear to be unresponsive until DCOM times out.

RESOLUTION

To resolve this problem:
  • Design your applications to handle user input on threads that are different from those threads that create remote COM+ objects.
  • Try to create an object again after an unsuccessful attempt.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

APPLIES TO
  • Microsoft Application Center 2000 Standard Edition
  • Microsoft Application Center 2000 Service Pack 2
Keywords: 
kbprb KB820448
       

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