Message Queuing Life

Question

How do you manage the message lifetime in a message queue? What is the default life span? I tried to run message queues locally, and found that messages disappear when the system reboots. Doesn't that destroy the purpose of the message queue when building loosely coupled applications. Does this mean when messages are sent to another computer for processing, the next day they will not be available. Some of the recommendations here are much appreciated since I do not quite understand these aspects of the message queuing system.

Answer 1

There are two types of messages without transactions. There is an express message and a recoverable message. The express message will be deleted on the server (or the msmq service, I think), restart. The bright message is the default view in the .net api and in the com api. To make the message persistent, you must set the Recoverable property to true. Here is the plumber's explanation .

There are other properties for controlling the lifetime of a message. But their default is forever.

Remember also that these are message properties, not queue properties.

Answer 2

What do you set for the TimeToBeReceived property?

Message queues are stored on disk, so a reboot should not get rid of them if they have not expired.

, , , - , .

-Adam