Not receiving messages when multi tenancy is configured for Azure Service Bus

[roeldewit]

Describe the bug
I configured Wolverine to use Azure Service Bus and added a tenant by connection string, this results in Wolverine not receiving any messages anymore.

To Reproduce
I created a sample solution to easily reproduce this bug, it can be found here: https://github.com/roeldewit/wolverinetest

It consists of a Sender API that has a single HTTP GET method, accessible via Swagger, to publish a test message to the service bus.

Besides that it has a Receiver API that has a message handler, which simply logs the content of the received message.

When you run it as is, the Sender API will successfully publish the test message, but it will not be received by the Receiver API.

If you remove line 19 in the Program.cs of the Sender API, it will function correctly again.

Expected behavior
It continues receiving messages while taking into account the configured tenants.

Desktop

• OS: Windows 10
• .NET 9
• Visual Studio 2022

Additional context
I redacted the connection strings of the Azure Service Bus, but I used two separate instances with the Standard tier.

[jeremydmiller]

Some extra context:

  GH-1933 (investigation only): The root cause is that AzureServiceBusTransport.BuildListenerForQueue() creates a CompoundListener with listeners for both the default transport and each tenant. When
  tenants use separate Service Bus namespaces (via AddTenantByConnectionString), the default listener listens on the wrong namespace. The recommended fix is to detect when tenant connection strings point
   to different namespaces and either skip the default listener or warn users to configure GlobalListener().

[jeremydmiller]

Closed by #2177