Azure Service Bus dead-letter queues not receiving messages

[kakins]

Describe the bug Native Azure Service Bus dead letter queues do not appear to work as described in the documentation. When a handler encounters and exception after exhausting all retries, an error message is sent to the wolverine-dead-letter-queue but not the associated ASB DLQ.

To Reproduce

builder.Host.UseWolverine((context, opts) =>
{
    opts.MessageExecutionLogLevel(LogLevel.Debug);
    var azureServiceBusConnectionString = "...";

    opts.UseAzureServiceBus(azureServiceBusConnectionString)
        .AutoProvision()
        .ConfigureListeners(listener => 
        { 
            listener.UseDurableInbox(new BufferingLimits(500, 100)); 
        });
    opts
        .PublishMessage<CreateIssue>()
        .ToAzureServiceBusQueue("create-issue")
        .ConfigureQueue(q => q.MaxDeliveryCount = 1);
    opts
        .ListenToAzureServiceBusQueue("create-issue");
});

var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    app.UseSwagger();
    app.UseSwaggerUI();
}

app.UseHttpsRedirection();

app.MapPost("/issues/create", (CreateIssue body, IMessageBus bus) => bus.SendAsync(body));

app.Run();

public record CreateIssue(Guid OriginatorId, string Title, string Description);

public class CreateIssueHandler
{
    public async Task<IssueCreated> Handle(CreateIssue command)
    {
        throw new Exception();
    }
}

Screenshots

[jeremydmiller]

@kakins Making the listener durable is going to make it use the database as the DLQ.

So the docs need to be fine tuned a bit:

• If an Azure Service Bus queue listener is Inline (Buffered is the default), then Wolverine uses the native DLQ functionality
• If an Azure Service Bus queue listener is Buffered or Durable, Wolverine will use the database storage as the DLQ -- if there is one configured

Try changing this to "Inline" for now. And I'll label this for now as a docs issue.

[kakins]

@jeremydmiller That did it! Thanks!