Limitations when working with MSMQ
Although QueueExplorer makes queues and messages look similar to folders and files, under the hood most functionality is performed using standard Receive, Send, or Peek operations. Operations which modify or create new messages will Send operation will always put new message on the end of the queue, unless message priority affects that.
- When you load, copy, drag&drop or edit message it will go to the end of queue.
- Higher priority messages will be listed above lower priority messages, unless they are sorted by some field.
- When messages are copied, moved, saved, loaded, some properties will be changed. For example: sender, time sent, time arrived, etc.
- QueueExplorer doesn’t update display in real time. If some other application or another QueueExplorer window modifies some queue, you have to use “Refresh” to see these changes.
- Some operations could fail or produce undesirable results if messages are removed in the mean time by some other program. It’s advisable to stop other processes that use queue while operations like copy, move, etc. are performed.
- If journaling is enabled messages removed from queue will show up in the journal if they are in any way removed from queue - in case of delete, cut, move, send to back, etc.
Remote MSMQ limitations
- Public queues will not be available if local MSMQ is installed in Workgroup mode.
- It’s not possible to programmatically determine if remote queue is transactional or not. Without that information message can not be sent. First time something is sent user must tell QueueExplorer whether remote queue is transactional or not.
- New queues cannot be created.
- Properties of remote queues are not available.
- Only summary data is available for outgoing queues.