(Curious you should be talking about ghosts...)
Now you call these messages "ghost messages". To me this implies the message
has already arrived 2 months ago and been processed (so is dead) but has
re-appeared. Is this the case? Are these really messages that have
definitely guaranteed been processed before?
Maybe there are machines out there that have messages to deliver but do not
have good network connectivity - laptops used by people on the road are a
good example.
Once a message has been sent by an application, MSMQ will keep trying to
deliver it forever (or until the Time To Reach Queue value has been reached,
if one has been set).
So the only way to stop other messages arriving is to find the sending
machine and purge them from that machine's outgoing queue.
A different (and unlilely) cause can be some weird networking problem which
caused a copy of the message to be lost in the ether somewhere.
MSMQ has an internal mechanism built in to prevent duplicate messages
arriving:
http://blogs.msdn.com/johnbreakwell/archive/2007/04/02/how-msmq-prevents-duplicate-messages.aspx
This mechanism is good for catching duplicates up to 30 minutes after
originally sent.
I find it difficult to see, though, a duplicate message surviving 2 months
in limbo before finally reaching your machine but I suppose its a
possibility.
Will this affect performance? Depends - is it 10 messages or a million?
Cheers
John Breakwell (MSFT)
"jimi hendrix" <jimih...@discussions.microsoft.com> wrote in message
news:AE8D3199-F1C2-4E7B...@microsoft.com...