MSMQ 4.0 poison sub-queue
Does dynaTrace 5.6 support monitoring of poison MSMQ messages (messages that end up in the poison sub-queue) ?
When a message is picked up and processed, if an error occurs, the message then moves to a 'retry' sub-queue. Upon retry, if error still occurs and retry max count has been exceeded, MSMQ will then move message to the 'poison' sub-queue. So my question is, whats the best way to configure DT to show that messages have arrived in a sub-queue (either retry or poison)
Can you fill us in what "poison sub-queues" are? dynaTrace can trace MSMQ messages and pick the queue name up that it gets send to. If the poison sub-queue is something that MSMQ manages where it puts a message that is not processed then we wont be able to identify this along the PurePath.
What we can however do is query MSMQ Performance Metrics through our Windows Performance Counter Monitor. I am sure MSMQ exposes some performance counters that shows the number of messages in a certain queue. I think thats your best bet in case I correctly assume what this poison sub-queue is all about
Andi
