Article ID: 321784
Article Last Modified on 2/19/2007
APPLIES TO
- Microsoft Message Queuing 3.0
This article was previously published under Q321784
SYMPTOMS
When you send messages to a remote computer and the network connection is lost, the application may have a 12-second to 17-second delay in response to the Message Queuing send function.
CAUSE
This behavior occurs because every five seconds, the Message Queuing Queue Manager tries to reconnect to target computers that do not have a working TCP/IP session. If the target computer is not available, this connection attempt can be blocked. Message Queuing uses a limited number of working threads to handle these network connections and local applications.
There is no limit to the number of working threads to retry these connection attempts. This can lead to all worker threads being tied up in connection attempts. There may be more than one worker thread attempting to connect to the same target computer. This can leave no worker threads available for local applications until one of the threads that is used for a connection attempt times out.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
The English version of this fix 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
------------------------------------------------------
15-May-2002 21:43 5.1.0.1023 606,208 Mqqm.dll
15-May-2002 21:42 5.1.0.1023 164,864 Mqrt.dll
STATUS
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 XP Service Pack 1.
MORE INFORMATION
This fix corrects the problem by limiting only one thread (at most) to try to connect to same target at the same time. Additionally, it reserves one thread for servicing requests that are made by local applications.
One possible workaround is to increase this thread pool by increasing the QMThreadNo registry value. This registry value is documented in the Registry Reference help file in the Windows 2000 Resource Kit.
Additional query words: kbMSMQ
Keywords: kbhotfixserver kbqfe kbbug kbfix kbwinxpsp1fix KB321784
