MSMQ Transport Configuration

Component: MSMQ Transport
NuGet Package NServiceBus.Transport.Msmq (1-pre)
Target NServiceBus Version: 7.x
This page targets a pre-release version and is subject to change prior to the final release.

Provides support for sending messages over [MSMQ](Provides support for sending messages over RabbitMQ).

Receiving algorithm

Because of how the MSMQ API has been designed, the receive algorithm is more complex than for other polling-driven transports (such as SQLServer).

The main loop uses GetMessageEnumerator2 to iterate over all messages available in the queue and creates a separate receiving task for each message.


The NuGet package includes two PowerShell scripts to help facilitate the queue creation and cleanup for an endpoint. The queues for the endpoint can be created via code by calling the EnableInstaller configuration Api, the code to create the queues is run every time the endpoint starts up.

To avoid this behavior, call this transport configuration Api to explicitly not create the queues even when the endpoint explicitly invokes the EnableInstaller.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();


Forwarding messages to the Dead Letter Queue is ON by default as a safety mechanism. The DLQ setting prevents message loss due to either bad configuration or any other reason where the message could not be delivered to the destination queue.

Call this API to disable the storing of undeliverable messages in the DLQ. This setting must only be used where loss of messages is an acceptable scenario. Writing to the DLQ can add performance overhead. In high volume scenarios it can be turned off. However, when doing so, it's essential to ensure that the routing configuration is accurate, as it can lead to message loss otherwise.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();


By default, caching is set to true and instructs MSMQ to cache connections to a remote queue and re-use them as needed instead of creating new connections for each message. This API allows connection caching to be turned off. However doing so will negatively impact the message throughput in most scenarios.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();


This setting should be used with caution. As the queues are not transactional, any message that has an exception during processing will not be rolled back to the queue. Therefore this setting must only be used where loss of messages is an acceptable scenario.

While there may be a performance gain when using non-transactional queues, it should be carefully weighed against the possibility of message loss.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();
This setting is not the same as using TransactionMode.None. This setting implies that the physical queue where the messages will be stored will not be a transactional queue. Endpoints that use non-transactional queues will not be able to send messages to endpoints that use transactional queues. Therefore it is important for all the endpoints that intend to communicate with each other to use the same setting.


This API Enables the use of journaling messages. With this option, MSMQ will store a copy of every message received and processed in the journal queue.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();

WARN: This setting should be used ONLY when debugging as it can potentially use up the MSMQ storage quota based on the message volume.


Overrides the TTRQ timespan. The default value if not set is Message.InfiniteTimeout.

TTRQ is the time limit for the message to reach the destination queue, beginning from the time the message is sent. This sets the underlying Message.TimeToReachQueue.

Format must be compatible with TimeSpan.Parse.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();

MSMQ Label

This feature was added in Version 6 and can be used to communicate with Version 5 (and higher) endpoints. However it should not be used when communicating to earlier versions (2, 3 or 4) since in those versions the MSMQ Label was used to communicate certain NServiceBus implementation details.

Often when debugging MSMQ using native tools it is helpful to have some custom text in the MSMQ Label. For example the message type or the message id. As of Version 6 the text used to apply to Message.Label can be controlled at configuration time using the ApplyLabelToMessages extension method. This method takes a delegate which will be passed the header collection and should return a string to use for the label. It will be called for all standard messages as well as Audits, Errors and all control messages. The only exception to this rule is received messages with corrupted headers. In some cases it may be useful to use the Headers.ControlMessageHeader key to determine if a message is a control message. These messages will be forwarded to the error queue with no label applied. The returned string can be String.Empty for no label and must be at most 240 characters.

var transport = endpointConfiguration.UseTransport<MsmqTransport>();
// Set the msmq message label to the current Message Id
    labelGenerator: headers =>
        return headers[Headers.MessageId];

Transactions and delivery guarantees

MSMQ Transport supports the following Transport Transaction Modes:

  • Transaction scope (Distributed transaction)
  • Transport transaction - Sends atomic with Receive
  • Transport transaction - Receive Only
  • Unreliable (Transactions Disabled)

See also Controlling Transaction Scope Options.

Transaction scope (Distributed transaction)

In this mode the ambient transaction is started before receiving the message. The transaction encompasses all stages of processing including user data access and saga data access.

Native transactions

In Versions 6.1 and above, the MSMQ transport uses native transactions to support the ReceiveOnly and SendsAtomicWithReceive levels. With SendsAtomicWithReceive the native transaction for receiving messages is shared with sending operations. That means the message receive operation, and any send or publish operations, are committed atomically. When using ReceiveOnly, the transaction is not shared with sending operations and dispatched messages may not be rolled back in case the receiving transaction needs to abort.

Version 6.0 does not distinguish between ReceiveOnly and SendsAtomicWithReceive and both levels behaving as SendsAtomicWithReceive.

Unreliable (Transactions Disabled)

In this mode, when a message is received, it is immediately removed from the input queue. If processing fails the message is lost because the operation cannot be rolled back. Any other operation that is performed, when processing the message, is executed without a transaction and cannot be rolled back. This can lead to undesired side effects when message processing fails part way through.

Related Articles

Last modified