Microsoft KB Archive/822455

= The Message Queuing Trigger Service Causes 100% CPU Use =

Article ID: 822455

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Message Queuing 2.0

-





SYMPTOMS
The Message Queuing Trigger service causes 100 percent CPU use.



CAUSE
This problem occurs because a map object is changed while a thread is in read lock. This means that multiple threads can change the same map and possibly corrupt the map. A critical section was added to serialize access when the map is updated.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next version of the Message Queuing Trigger service that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version            Size    File name 16-Jun-2003 14:15  2.4.1.0         4,528,033  Msmqtriggers.exe 16-Jun-2003 14:14  1.1.3.0            98,396  Setupextended.dll 16-Jun-2003 14:14                    360,508  Trigadm.exe 16-Jun-2003 14:14  1.1.0.24           77,881  Trigmon.exe 16-Jun-2003 14:13  1.1.0.24          368,702  Trigobjs.dll 16-Jun-2003 14:13  1.1.0.24          323,646  Trigserv.exe 16-Jun-2003 14:14  1.1.0.24          536,634  Trigsnap.dll 16-Jun-2003 14:14                        986  Trigsnap.exp 16-Jun-2003 14:14                      2,616  Trigsnap.lib 16-Jun-2003 14:14  1.1.0.24          122,969  Uninst.dll



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

Keywords: kbqfe KB822455

-

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

© Microsoft Corporation. All rights reserved.