FIX: AV in MSMQ Queue Manager When Application Reuses Internal Transaction Object (280090)


The information in this article applies to:

  • Microsoft Message Queuing 2.0
This article was previously published under Q280090

SYMPTOMS

When an application uses the MSMQ internal transaction object multiple times, the MSMQ Queue Manager may cause an access violation (AV).

CAUSE

Internally, the MSMQ internal transaction object is not invalidated after a commit is done. Applications that are coded to just reuse this object after commit (instead of doing a new MQBeginTransaction) could cause a race condition that would cause an AV in the MSMQ service.

Reuse of transactional objects after commit is not legal, and the Queue Manager should not allow this. This problem is very dependent on timing, and applications may be coded in this manner without causing the race condition if a sufficient amount of time elapses between send/receives within the transactions.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix.

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

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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 typical 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 fix should have the following file attributes or later:
   Date          Time   Version       Size   File name     
   -------------------------------------------------------
   28-FEB-2001   17:54  5.0.0.720    273KB   Mq1repl.dll
   28-FEB-2001   17:47  5.0.0.720     14KB   Mq1sync.dll
   28-FEB-2001   17:47  5.0.0.733     70KB   Mqac.sys
   28-FEB-2001   17:54  5.0.0.721    210KB   Mqads.dll
   28-FEB-2001   17:47  5.0.0.720     22KB   Mqbkup.exe
   28-FEB-2001   17:54  5.0.0.720     29KB   Mqcertui.dll
   28-FEB-2001   17:54  5.0.0.720     49KB   Mqclus.dll
   28-FEB-2001   17:54  5.0.0.720     30KB   Mqdbodbc.dll
   28-FEB-2001   17:54  5.0.0.720     74KB   Mqdscli.dll
   28-FEB-2001   17:54  5.0.0.720     41KB   Mqdssrv.dll
   28-FEB-2001   17:47  5.0.0.720     96KB   Mqmig.exe
   28-FEB-2001   17:54  5.0.0.720    258KB   Mqmigrat.dll
   28-FEB-2001   17:54  5.0.0.720    219KB   Mqoa.dll
   28-FEB-2001   17:54  5.0.0.720      8KB   Mqperf.dll
   28-FEB-2001   17:54  5.0.0.733    406KB   Mqqm.dll
   28-FEB-2001   17:54  5.0.0.720      9KB   Mqrperf.dll
   28-FEB-2001   17:54  5.0.0.733     90KB   Mqrt.dll
   28-FEB-2001   17:54  5.0.0.720     69KB   Mqsec.dll
   28-FEB-2001   17:54  5.0.0.720    391KB   Mqsnap.dll
   28-FEB-2001   17:48  5.0.0.720     14KB   Mqsvc.exe
   28-FEB-2001   17:54  5.0.0.720     24KB   Mqupgrd.dll
   28-FEB-2001   17:54  5.0.0.720    106KB   Mqutil.dll
   28-FEB-2001   17:54  5.0.0.720     64KB   Msmq.cpl
   28-FEB-2001   17:54  5.0.0.720    156KB   Msmqocm.dll

STATUS

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

MORE INFORMATION

The code now checks to see whether the transaction object is valid and returns an error to the application if it tries to reuse the object after a commit was done with this object.
Modification Type:MinorLast Reviewed:10/7/2005
Keywords:kbfix kbprb kbQFE KB280090
©2004 Microsoft Corporation. All rights reserved.