Unexpected entries in SubscriptionRouting

[rioka]

Describe the bug

Description

When the bridge is used to connect 2+ SQLServer transports, unexpected entries are found in SubscriptionRouting in all databases

Expected behavior

Subcriptions should be added only in transports used by actual subscribers

Actual behavior

Subscriptions are added in all connected transports

Versions

• NServiceBus.MessagengBridge v4.0.3

Steps to reproduce

Sample project reproducing the issue is available here

Relevant log output

Additional Information

Workarounds

Possible solutions

Additional information

[ramonsmits]

@rioka Thanks for sharing this. We've analyzed this today.

var notifierTransport = new BridgeTransport(new SqlServerTransport(notifierConnectionString))
{
    Name = "SQL-Notifier",
    AutoCreateQueues = true
};
var notifierEndpoint = new BridgeEndpoint("Notifier");
notifierEndpoint.RegisterPublisher("Shared.ClientOrderReceived, Shared, Version=1.0.0.0", "Receiver");

It seems that the above code currently seems to behave as:

• For every transport that does not have the notifierEndpoint, subscribe to that event

While it should be

• For the transport that has "Receiver", subscribe to that event

We'll do a bug triage next week and share the results on this issue.

[danielmarbach]

Hi @rioka. We've reviewed this bug and added it to our backlog. It is not currently prioritized, but it may be fixed along with other future work in the repository. We will update this issue when work begins.

[rioka]

Hi @rioka. We've reviewed this bug and added it to our backlog. ...

👍 Great!
Thanks