The RabbitMQ transport requires a connection string to connect to the RabbitMQ broker. While RabbitMQ uses the AMQP URI Specification, the RabbitMQ transport uses its own connection string format.
To specify the connection string in code:
var transport = busConfiguration.UseTransport<RabbitMQTransport>(); transport.ConnectionString("My custom connection string");
By default, the transport will look for a connection string called
<connectionStrings> <add name="NServiceBus/Transport" connectionString="host=broker1"/> </connectionStrings>
To use a custom name for the connection string:
var transport = busConfiguration.UseTransport<RabbitMQTransport>(); transport.ConnectionStringName("MyConnectionStringName");
Below is the list of connection string options. When constructing a connection string, these options should be separated by a semicolon.
The host name of the broker.
By default, the guest user can only connect via localhost. If connecting to a remote host, a user name and password must be provided.
<connectionStrings> <add name="NServiceBus/Transport" connectionString="host=myremoteserver; username=myusername; password=mypassword"/> </connectionStrings>
The port where the broker listens.
5671 if the
UseTls setting is set to
true, otherwise the default value is
The virtual host to use.
The user name to use to connect to the broker.
The password to use to connect to the broker.
The interval for heartbeats between the endpoint and the broker.
The time period allowed for the dequeue strategy to dequeue a message.
The number of messages to prefetch when consuming messages from the broker.
Default: The number of configured threads for the transport (as of Version 2.1)
Controls if publisher confirms should be used.
How long the client should wait for publisher confirms, if enabled.
The time to wait before trying to reconnect to the broker if the connection is lost.
The default connection manager that comes with the transport is usually good enough for most users. To control how the connections with the broker are managed, implement a custom connection manager by inheriting from
IManageRabbitMqConnections. This requires that connections be provided for:
- Administrative actions like creating queues and exchanges.
- Publishing messages to the broker.
- Consuming messages from the broker.
In order for the transport to use the above, register it as shown below:
var transport = busConfiguration.UseTransport<RabbitMQTransport>(); transport.UseConnectionManager<MyConnectionManager>();
The RabbitMQ transport monitors the connection to the broker and will trigger the critical error action if the connection fails and stays disconnected for the configured amount of time.
Controls the amount of time the transport waits after a failure is detected before triggering the critical error action.
00:02:00 (2 minutes)
<appSettings> <add key="NServiceBus/RabbitMqDequeueStrategy/TimeToWaitBeforeTriggering" value="00:02:00"/> </appSettings>
Controls the amount of time the transport waits after a failure is detected before trying to poll for incoming messages again.
00:00:05 (5 seconds)
<appSettings> <add key="NServiceBus/RabbitMqDequeueStrategy/DelayAfterFailure" value="00:00:05"/> </appSettings>
For debugging purposes, it can be helpful to increase the
DequeueTimeout settings as shown below:
<connectionStrings> <add name="NServiceBus/Transport" connectionString="host=broker1;RequestedHeartbeat=600;DequeueTimeout=600"/> </connectionStrings>
Increasing this setting can help avoiding the connection timeout while the debugging.