Help Needed: MSMQ, Queued Components and disk storage clean up

[Paul Widner]

Hello I need some help if possible. I have developed a new system that
utilizes queued components and private queues. I have one system that
monitors a DB table for new records and makes
GetObject(queue:FormatName=DIRECT=OS:SERVERNAME\PRIVATE$\pm/new:ProgName.Cla
ssName) calls to various other systems for processing of these new records.
These other systems contain the queued COM+ applications and thus the
private MSMQ. The problem I am having is that the sending system's MSMQ
storage files are never getting cleaned up. On the other had the receiving
system's file are getting cleaned up fine. I have tried adding the
MessageCleanUpInterval registry entry but this has had no effect. This is
becoming an issue quickly as we are processing a large volume of messages
and MSMQ is utilizing 1.7 gigs of disk space as well and the same amount of
RAM when MSMQ is started. Is this a known bug or is there some
configuration that I don't know about?

Thanks,
PaulW

[Doron Juster [MSFT]]

Messages files are deleted only when they are empty. Each file can contain
many messages. It's enough that one of the messages is valid and file will
not be deleted. a common mistake is that applications do not cleanup journal
queues or the deadletter queue. Make sure that all these queues are
cleaned-up periodically.
You can use perfmon counters to see which queues are non-empty.

Thanks, Doron
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Paul Widner" <paul_...@hotmail.com> wrote in message
news:uBLsPsuoCHA.1988@TK2MSFTNGP09...

[Paul Widner]

I've included the text from my PrefMon log.

(PDH-CSV 4.0) (US Mountain Standard Time)(420)

\\TRAMSDW01\MSMQ Queue(os:tramsapp01\private$\pm)\Bytes in Queue 0

\\TRAMSDW01\MSMQ Queue(os:tramsapp02\private$\pm)\Bytes in Queue 0

\\TRAMSDW01\MSMQ Queue(os:w2krms01\private$\pm)\Bytes in Queue 0

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\admin_queue$)\Bytes in

Queue 0

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\inventory manager)\Bytes

in Queue

138984

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\inventory manager_4)\Bytes

in Queue

1780

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\inventory

manager_deadqueue)\Bytes in Queue

29568

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\notify_queue$)\Bytes in

Queue

0

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\order_queue$)\Bytes in

Queue

0

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\pm_deadqueue)\Bytes in

Queue

1160

\\TRAMSDW01\MSMQ Queue(tramsdw01\private$\rms)\Bytes in Queue

150892

Note at the same time mqsvc.exe was taking up 1,316,376K or memory.

Does this make sense that it would still use this huge amout of memory?

Paul

"Doron Juster [MSFT]" <Dor...@Microsoft.com> wrote in message
news:e$yJ0JEpCHA.1948@TK2MSFTNGP10...

[Paul Widner]

Ah I have found the issue. I was unaware that when you purge a queue that an
entry was added to the "Transactional dead-letter messages" System Queue.
Once I purged this queue MSMQ quickly cleaned up.

Thanks,

Paul

"Paul Widner" <paul_...@hotmail.com> wrote in message

news:eMGFhNfpCHA.2000@TK2MSFTNGP12...