1. One sets HKEY_LOCAL_MACHINE
\Software\Microsoft\MSMQ\Parameters\TcpNoDelay with
Data Type: REG_SZ
String: 1
2. And the other HKEY_LOCAL_MACHINE
\Software\Microsoft\MSMQ\Parameters\TCPNoDelay with
Data Type: REG_DWORD
Hex: 1
We tried option 2 and saw great improvement on Windows 2000 but are confused
which documentation to forward to our client - which one is correct or will
both work?
Another question: how can I determine which version of msmq I am running?
Thanx in advance.
Alice
It's possible both would work (have you tried it?) but I believe REG_DWORD
is correct. The original KB article that fixed the problem and the current
registry reference both suggest it is a DWORD.
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B241777
http://technet2.microsoft.com/WindowsServer/en/Library/e6491291-872e-4260-8ced-77525b0d79a51033.mspx
> Another question: how can I determine which version of msmq I am running?
MSMQ version is very closely tied to the Operating System. MSMQ 1.0 runs on
Windows NT Server and Workstation, MSMQ 2.0 runs on Windows 2000 Server and
Professional and MSMQ 3.0 runs on Windows Server 2003 and Windows XP. The
easiest way to tell which MSMQ you are running is to look at the version of
Operating System you ware running.
If you are running on Windows XP, the property PROPID_MGMT_MSMQ_TYPE will
give you an MSMQ version string but that property is almost useless since it
only works on XP and if your on XP you already know you are running MSMQ
3.0.
The PROPID_PC_VERSION property is slightly more useful. It was introduced
in MSMQ 2.0 and can be retrieved using the MQGetPrivateComputerInformation
function (also introduced in MSMQ 2.0). You can use the property to tell
which version of MSMQ you are running (assuming you are running MSMQ 2.0 or
later) and you can infer that you are running on MSMQ 1.0 if the property
and function are not supported.