Many connections opened for IModel

[basilfx]

I'm using the code below, based on the examples in the wiki. It is an Azure Function V3 function, using .NET Core 3.1. I'm running this locally.

Whenever I run this, I notice that I have a lot of open connections, up to a point where I'm running out of connections and the application stalls. The RabbitMQ Management Interface shows all these connections as well, and they all disappear when I kill the application. To my understanding, channels are multiplexed on a single connection, so I would assume a single connection, instead of a connection per function invocation. Therefore, I think this is a bug.

As a 'work-around', I now inject a my own IConnection in my function class, then use using (var channel = connection.CreateModel() { .. } which works as expected. I also notice that it is faster: I was managing 5 msg/sec, now 25 msg/sec.

Code:

[FunctionName("FunctionName")]
public async Task RunAsync(
    [RabbitMQTrigger(
        "QueueName",
        ConnectionStringSetting = "ConnectionString")]
    BasicDeliverEventArgs message,
    [RabbitMQ(ConnectionStringSetting = "ConnectionString")]
    IModel channel)
{
    // Some processing of the message here.
    // ...

    // Publish updates to an exchange
    var batch = channel.CreateBasicPublishBatch();

    foreach (var update in updates.Values)
    {
        var (body, properties) = MessagingHelper.ToMessage(update, message);

        batch.Add(
            exchange: "ExchangeName",
            routingKey: "",
            mandatory: false,
            properties: properties,
            body: body);
    }

    batch.Publish();

    // Doesn't help
    // channel.Close()
}

[Socolin]

I confirm the problem I just experimented this after deploying a new version of our app in production.

This is blocking our deployment, could you please fix this soon ?

@jeffhollan This project seems dead again can we expect a fix soon ? or should I found another way to fix this on my own ?

[yojagad]

Thanks for reporting. I'll take a look at this and possibly send a fix