How do I tell if the MSMQ is working properly?

[black_13]

How do I tell if the MSMQ is working properly?

Here is my problem I am using Embedded XP, which is essentially XP,
same kernel, same registry,
so forth. I have a large number of machines that are currently
deployed recently but were
deployed without MSMQ core functionality. It has now been determined
that MSMQ needs
to be running on these machines. I have to good fortune in that I can
push files to the machines
and cause the machines to run such utilities such as reg. What I have
done is scraped
all the files that I think are needed for MSMQ and cause SYSOCMGR to
install MSMQ core
on these machines. But how do test that MSMQ is really running
correctly?

Thanks
black_13

[Frank Boyne]

"black_13" <jjos...@gmail.com> wrote in message
news:9923b8dd-acfe-4e14...@m3g2000hsc.googlegroups.com...

> But how do test that MSMQ is really running
> correctly?

To some extent that depends on how you are going to be using MSMQ on
these machines - ideally your tests should reflect your real-world use.

Perhaps the most simple test would be to make some sort of MSMQ function
call and check that you get the expected result. For example, you could
call MQPathNameToFormatName on a path like ".\private$\dummyq". If MSMQ
is running okay you should get an indication that the path name is not
vald (queue doesn't exist). Or you could call MQOpenQueue on a queue
you know should exist (like the dead letter queue).
http://msdn2.microsoft.com/en-us/library/ms706227.aspx

A more elaborate test would be to create a local queue, send a message
to that queue and then read the message back.

If you are going to use MSMQ to access queues on other systems, an even
more elaborate test would be to send a message to a non-local queue and
then read the message back - or better yet, have another application
read the message your test sends and send a reply to a local queue which
your test can then check.

[John Breakwell (MSFT)]

Hi,

You can only say that a particular machine is "really" running correctly by
running a whole range of tests on it. An easier approach would be to
generate a TMQ STATE report which checks the file versions and registry
entries:

Description of TMQTools utilities for Microsoft Message Queuing

http://support.microsoft.com/kb/887220

Run "TMQ STATE -V -D" and have a look through TMQSTATE.LOG to see if the
report shows a healty status.

Cheers

John Breakwell

"black_13" <jjos...@gmail.com> wrote in message
news:9923b8dd-acfe-4e14...@m3g2000hsc.googlegroups.com...