You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: transports/msmq/troubleshooting.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: MSMQ Transport Troubleshooting
3
3
summary: Resolutions for common problems with the MSMQ transport.
4
-
reviewed: 2022-02-09
4
+
reviewed: 2024-10-24
5
5
component: MsmqTransport
6
6
isLearningPath: true
7
7
redirects:
@@ -61,7 +61,7 @@ Also, check the outgoing queues to see if messages sent to remote servers are re
61
61
1. Make sure that the hard disk drive has sufficient space.
62
62
1. Disable the MSMQ storage limit if the disk still has plenty of space.
63
63
1. Inspect the (transactional) dead-letter queue (TDLQ) under System Queues via [QueueExplorer by Cogin](https://www.cogin.com/mq/) as the built-in viewer for Windows has limitations.
64
-
* Dead-letter queues acts as a recycle bin for other transactional queues. If other transactional queues have been purged, ensure the TDLQ is purged as well.
64
+
* Dead-letter queues act as a recycle bin for other transactional queues. If other transactional queues have been purged, ensure the TDLQ is purged as well.
65
65
* Within the TDLQ, the Class column shows the reason the message arrived there. Common messages include "The queue was purged" or "The queue was deleted".
66
66
* Purge the content of the TDLQ/DLQ to free storage space.
67
67
1. Inspect outgoing queues for messages that cannot be delivered due to connectivity issues, or machines that are unavailable or obsolete. Resolve connectivity issues to ensure queued outgoing messages will be delivered to the remote machine(s).
@@ -106,7 +106,7 @@ Outgoing queues show three values:
106
106
- Unacknowledged (msgs)
107
107
- Unprocessed (msgs)
108
108
109
-
By default *Number of messages* shows the count of messages that have not yet been delivered or processed. It does not indicate the number of messages that still need to be sent. Calculate the number of unsent messages by subtracting *Unprocessed (msgs)* from *Number of messages*.
109
+
By default,*Number of messages* shows the count of messages that have not yet been delivered or processed. It does not indicate the number of messages that still need to be sent. Calculate the number of unsent messages by subtracting *Unprocessed (msgs)* from *Number of messages*.
110
110
This means that if an endpoint at the recipient is stopped or slow, the messages remaining to be processed are included in this count.
111
111
112
112
When MSMQ dead-lettering is disabled *Number of messages* will only indicate the number of messages remaining to be delivered. *Unprocessed (msgs)* will always show the value 0 when dead lettering is disabled.
@@ -125,7 +125,7 @@ The following precautions can be taken to monitor the health of MSMQ in a produc
125
125
126
126
Define thresholds for the performance counters. Then create alerts that are triggered when the thresholds are exceeded. The alerts can be integrated with monitoring suites like Solarwinds, New Relic, SCOMM, or similar tools.
127
127
128
-
To determine useful thresholds, determine what values are typical for the specific environment to act as a baseline. This helps detect and address potential issues early, e.g. before MSMQ reaches its limits with regards to disk and memory usage.
128
+
To determine useful thresholds, determine what values are typical for the specific environment to act as a baseline. This helps detect and address potential issues early, e.g. before MSMQ reaches its limits in regard to disk and memory usage.
0 commit comments