We have a mobile tracking system written in VB dependent on MSMQ to pass transactions to the server as carriers move in and out of network coverage across the plant. We have seen that the messages queue up for maybe 30-45 minutes or more and then may be passed in a bunch, and yet the carrier is still within the wireless coverage. The mobile PCs are on W2000 SP4. So we attempted to log that more than a few messages are queued up within coverage. These calls to MQMgmtGetInfo have trashed the OS.
So we either need to solve the real issue with the messages queueing up for an unknown reason within coverage or be able to log when, and try to discover what the underlying issue is.
Has anyone seen this? Do you have suggestions? Should we write the MQMgmtGetInfo calls in a C-based DLL?