Note that there are some explanatory texts on larger screens.

plurals
  1. POMSMQ using questions
    primarykey
    data
    text
    <p>Can you explain, how much RAM memory will be used when using recoverable messages? I know, that one message consumes approximately 70–80 bytes and this is ok and i know that message body will save to the disk, but may it also duplicates body to the RAM? I tried to test that with express and recoverable message (message storage limit is 1gb) — and in both case i see in process explorer, that msmq service process reached his working set (memory) to 1gb. I understand that in case of express messages it's ok, but with recoverable messages it shoud be much less!</p> <p>And the second question is about MSMQ callback limitation.</p> <blockquote> <p>If you receive messages with callback, consider that each process can register only up to 63 callbacks. If your callbacks wait on queues indefinitely without activity, you may reach this limit.</p> </blockquote> <p>Is it applies to all queues or only to one? For example, i have i process and i do something like:</p> <pre><code>QueueFirst = new MessageQueue(@".\test") { Formatter = new BinaryMessageFormatter() }; QueueFirst.ReceiveCompleted += QueueOnReceiveCompleted; QueueSecond = new MessageQueue(@".\test") { Formatter = new BinaryMessageFormatter() }; QueueSecond.ReceiveCompleted += QueueOnReceiveCompleted; for (int i = 0; i &lt; 63; i++) { QueueFirst.BeginReceive(TimeSpan.FromSeconds(10), "", Callback); QueueSecond.BeginReceive(TimeSpan.FromSeconds(10), "", Callback); } </code></pre> <p>Can i do that? I'm asking, because if i set upper cycle limit to value more than 63, nothing bad happens. I'm using this <a href="http://msdn.microsoft.com/en-us/library/c2hsyffy(v=vs.100).aspx" rel="nofollow">method overload</a>, because in help there is something about callbacks, is it means that using event handler doesn't have any limits?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload