Bridging audits from Sql to Msmq does not seem to work

[carl-berg]

Describe the bug

Description

I'm not sure if this is supposed to work, but it's showcased in the documentation:

var msmqBridgeTransport = new BridgeTransport(new MsmqTransport())
{
    AutoCreateQueues = true
};

/* ... some other endpoints configured */

msmqBridgeTransport.HasEndpoint("Particular.ServiceControl");
msmqBridgeTransport.HasEndpoint("error");
msmqBridgeTransport.HasEndpoint("audit");

Expected behavior

To not get an exception i guess 😄

Actual behavior

Bridge does not seem to be able to handle the audit messages

Versions

• NServiceBus 9.2.7
• NServiceBus.MessagingBridge 4.0.3
• NServiceBus.MessagingBridge.Msmq 4.0.3
• NServiceBus.Transport.SqlServer 8.1.9

Steps to reproduce

Sending a message from an sql transport endpoint to an msmq endpoint where the sending endpoint has audit enabled, the bridge will then fail to handle the audit message.

Relevant log output

Message shovel operation failed, message will be moved to bridge. Error@[dbo]@[MyDatabase]

Exception: 
System.Exception: Failed to shovel message for endpoint audit with id 274ba0c7-9302-4d37-baa8-49fa47765e92 from sqlserver to msmq ---> System.Exception: Failed to send message to address: audit@MyServerName ---> System.ArgumentException: Address contains multiple @ characters. Address supplied: 'MyEndpoint@[dbo]@[MyDatabase]'
Parameter name: address
   at NServiceBus.Transport.Msmq.MsmqAddress.Parse(String address) in /_/src/NServiceBus.Transport.Msmq/MsmqAddress.cs:line 23
   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.SendToDestination(TransportTransaction transaction, UnicastTransportOperation transportOperation) in /_/src/NServiceBus.Transport.Msmq/MsmqMessageDispatcher.cs:line 210
   --- End of inner exception stack trace ---
   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.ThrowFailedToSendException(String address, Exception ex) in /_/src/NServiceBus.Transport.Msmq/MsmqMessageDispatcher.cs:line 320
   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.SendToDestination(TransportTransaction transaction, UnicastTransportOperation transportOperation) in /_/src/NServiceBus.Transport.Msmq/MsmqMessageDispatcher.cs:line 246
   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, CancellationToken cancellationToken) in /_/src/NServiceBus.Transport.Msmq/MsmqMessageDispatcher.cs:line 38
   at NServiceBus.Raw.StartableRawEndpoint.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/RawEndpoints/StartableRawEndpoint.cs:line 79
   at TargetEndpointDispatcher.Dispatch(OutgoingMessage outgoingMessage, TransportTransaction transaction, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/TargetEndpointDispatcher.cs:line 30
   at MessageShovel.<TransferMessage>d__1.MoveNext() in /_/src/NServiceBus.MessagingBridge/MessageShovel.cs:line 61
   --- End of inner exception stack trace ---

Additional Information

Workarounds

Possible solutions

Additional information

[carl-berg]

I may have spoke to soon. The error message was from a previous attempt before i had upgraded NServiceBus.MessagingBridge to latest version and switched out msmq transport package to NServiceBus.MessagingBridge.Msmq. I will investigate this more thoroughly.

[carl-berg]

Sorry, i was a bit too quick to close this. Turns out when i was testing on my machine i didn't have all the services running, so the problem remains after the bridge upgrade. The system has two transports: msmq and sql. The bride is configured to bridge heartbeats, audits and errors to msmq. Here's an example of a flow that doesn't work all the way:

1. Endpoint A (sql) sends a command to endpoint B (msmq) //here audit seems to work
2. Endpoint B (msmq) sends a command to endpoint C (sql) // here audit seems to fail
3. Endpoint C (sql) sends a local command to itself //here audit seems to fail as well

Here's an example of the bridge-error headers produced in step 2:

{
    "NServiceBus.MessageId": "07c915b7-055e-4acc-b5e4-b36e0093e983",
    "NServiceBus.MessageIntent": "Send",
    "NServiceBus.RelatedTo": "2e19664b-906d-4cc0-ac8e-b36e0093dfb7",
    "NServiceBus.ConversationId": "c3c9546c-93a5-4cfa-8202-b36e0093dfb9",
    "NServiceBus.CorrelationId": "2e19664b-906d-4cc0-ac8e-b36e0093dfb7",
    "NServiceBus.OriginatingMachine": "MyMachine",
    "NServiceBus.OriginatingEndpoint": "SenderEndpoint",
    "$.diagnostics.originating.hostid": "755e1c1ef58fea0005a233f4a847ff48",
    "NServiceBus.ReplyToAddress": "SenderEndpoint@[dbo]@[SqlTransportDatabase]",
    "NServiceBus.ContentType": "text/xml",
    "NServiceBus.EnclosedMessageTypes": "MyMessage",
    "NServiceBus.Version": "7.2.0",
    "NServiceBus.TimeSent": "2025-10-06 08:58:31:905508 Z",
    "CorrId": "2e19664b-906d-4cc0-ac8e-b36e0093dfb7\\0",
    "NServiceBus.Bridge.Transfer": "msmq->sqlserver",
    "NServiceBus.ProcessingStarted": "2025-10-06 08:58:32:511741 Z",
    "NServiceBus.ProcessingEnded": "2025-10-06 08:58:36:093573 Z",
    "$.diagnostics.license.expired": "true",
    "$.diagnostics.hostid": "4183b9459440b0126f05c63bcd6a627c",
    "$.diagnostics.hostdisplayname": "MyMachine",
    "NServiceBus.ProcessingMachine": "MyMachine",
    "NServiceBus.ProcessingEndpoint": "ReceiverEndpoint",
    "traceparent": "00-741daca420bc78f3d67145a028c33ace-159550255e081adb-01",
    "NServiceBus.MessagingBridge.FailedQ": "audit",
    "NServiceBus.MessagingBridge.ExceptionInfo.ExceptionType": "System.Exception",
    "NServiceBus.MessagingBridge.ExceptionInfo.InnerExceptionType": "System.Exception",
    "NServiceBus.MessagingBridge.ExceptionInfo.HelpLink": null,
    "NServiceBus.MessagingBridge.ExceptionInfo.Message": "Failed to shovel message for endpoint audit with id 156fddea-f26d-41de-8e43-953a4e6bf037 from sqlserver to msmq",
    "NServiceBus.MessagingBridge.ExceptionInfo.Source": "NServiceBus.MessagingBridge",
    "NServiceBus.MessagingBridge.ExceptionInfo.StackTrace": "System.Exception: Failed to shovel message for endpoint audit with id 156fddea-f26d-41de-8e43-953a4e6bf037 from sqlserver to msmq\r\n ---> System.Exception: Failed to send message to address: audit@MyMachine\r\n ---> System.ArgumentException: Address contains multiple @ characters. Address supplied: 'SenderEndpoint@[dbo]@[SqlTransportDatabase]' (Parameter 'address')\r\n   at NServiceBus.Transport.Msmq.MsmqAddress.Parse(String address) in /_1/nservicebus.transport.msmq.sources/3.0.1/contentFiles/cs/net8.0-windows7.0/NSB.Transport.Msmq/MsmqAddress.cs:line 23\r\n   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.SendToDestination(TransportTransaction transaction, UnicastTransportOperation transportOperation) in /_1/nservicebus.transport.msmq.sources/3.0.1/contentFiles/cs/net8.0-windows7.0/NSB.Transport.Msmq/MsmqMessageDispatcher.cs:line 99\r\n   --- End of inner exception stack trace ---\r\n   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.ThrowFailedToSendException(String address, Exception ex) in /_1/nservicebus.transport.msmq.sources/3.0.1/contentFiles/cs/net8.0-windows7.0/NSB.Transport.Msmq/MsmqMessageDispatcher.cs:line 209\r\n   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.SendToDestination(TransportTransaction transaction, UnicastTransportOperation transportOperation) in /_1/nservicebus.transport.msmq.sources/3.0.1/contentFiles/cs/net8.0-windows7.0/NSB.Transport.Msmq/MsmqMessageDispatcher.cs:line 135\r\n   at NServiceBus.Transport.Msmq.MsmqMessageDispatcher.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, CancellationToken cancellationToken) in /_1/nservicebus.transport.msmq.sources/3.0.1/contentFiles/cs/net8.0-windows7.0/NSB.Transport.Msmq/MsmqMessageDispatcher.cs:line 37\r\n   at NServiceBus.Raw.StartableRawEndpoint.Dispatch(TransportOperations outgoingMessages, TransportTransaction transaction, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/RawEndpoints/StartableRawEndpoint.cs:line 77\r\n   at TargetEndpointDispatcher.Dispatch(OutgoingMessage outgoingMessage, TransportTransaction transaction, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/TargetEndpointDispatcher.cs:line 25\r\n   at MessageShovel.TransferMessage(TransferContext transferContext, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/MessageShovel.cs:line 77\r\n   --- End of inner exception stack trace ---\r\n   at MessageShovel.TransferMessage(TransferContext transferContext, CancellationToken cancellationToken) in /_/src/NServiceBus.MessagingBridge/MessageShovel.cs:line 93\r\n   at NServiceBus.Transport.Sql.Shared.ProcessStrategy.TryHandleMessage(Message message, TransportTransaction transportTransaction, ContextBag context, CancellationToken cancellationToken) in /_/src/NServiceBus.Transport.Sql.Shared/Receiving/ProcessStrategy.cs:line 46\r\n   at NServiceBus.Transport.Sql.Shared.ProcessWithTransactionScope.TryProcess(Message message, TransportTransaction transportTransaction, ContextBag context, CancellationToken cancellationToken) in /_/src/NServiceBus.Transport.Sql.Shared/Receiving/ProcessWithTransactionScope.cs:line 89",
    "NServiceBus.MessagingBridge.TimeOfFailure": "2025-10-06 08:58:38:786635 Z"
}

[tamararivera]

Hi Carl,
We have reviewed this bug and added it to our bug fix queue.
However, there is no ETA for when we will get to this bug as it may be prioritized behind other, more urgent bugs. We will update this issue when it has a team assigned and work begins.

[carl-berg]

Alright. To not get stuck we decided to change the setup so our service-control uses sql as transport and the bridge moves messages from msmq to sql instead.