COM+ Does Not Reach SetMaxThreads for the Package

This article was previously published under Q255054
This article has been archived. It is offered "as is" and will no longer be updated.
An application, such as ASP in Internet Information Services (IIS) 5.0, that uses COM+ to manage a thread pool may experience poor performance because COM+ does not increase the thread count in the pool. Under normal conditions, COM+ increases the threads in the thread pool up to the maximum thread limit set by the SetMaxThreads method for the package. However, if the initial worker threads in the pool are too busy, then this issue may occur.

For example, when the ASP work load on an IIS 5.0 computer increases so that each worker thread uses up a considerable amount of time to complete each request, COM+ may never create any more threads even though the work in the shared queue is always increasing, which in this case, causes ASP queuing to occur. This problem can be identified by monitoring CPU usage. This problem will show up when CPU utilization by Inetinfo is very low, usually on long blocking calls.
Under heavy load, it is possible that the thread pool monitoring thread is not spin up. When this happens, additional threads are not added as needed. The thread pool monitoring thread must always be active.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.The following files are available for download from the MicrosoftDownload Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

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

This problem was first corrected in Windows 2000 Service Pack 1.
COM+ Thread Pool

Identyfikator artykułu: 255054 — ostatni przegląd: 10/20/2013 17:36:19 — zmiana: 3.8

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Internet Information Services 5.0

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbqfe kbthread KB255054
ERROR: at System.Diagnostics.Process.GetProcessHandle(Int32 access, Boolean throwIfExited) at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)