I am having an issue with MSMQ where messages periodically get stuck in the outbound queues in an unacknowledged state.
If I look at the outbound queues, I see 100% of the messages are in the Unacknowledged column and the Unprocessed column says '0' messages. The state for the queues is 'Connected'.
No errors in the event log and the NSB endpoints are not reporting any errors. It always happens during the overnight hours when my processing volume is low.
The only way I have found to resolve the issue is to restart MSMQ service on the sender and receiver machine. On occasion MSMQ does not want to restart on the distributor (receiver) and we end up reinstalling it
We have an open ticket with Microsoft, but they are not able to help us unless they have a trace file or they can inspect the servers during the issue. The trace we can not leave running because it fills up too quickly (2 minutes) and we always have the issue in the early morning on the East Coast and the MS support folks are on Pacific time.
Any advice is greatly appreciated.
I have a growing concern that MSMQ is not the right choice of transport. It does not seem to indicate when it has problems and just fails silently.
NServiceBus 5.2.0
Windows Server 2008 R2
Heavy use of DataBus
All servers have static IP
There is no NAT involved in networking
The MQId is different on all the servers
The Queues are all transactional