有没有详细的异常堆栈

比较了一下1.15和1.18版本的DbContextPool.cs的代码，这个clear导致的？

我刚刚回到家，我晚上我来测试一下，我有工具可以测试的

同样的昨天我也遇到连接池满的问题,

引发了异常: System.Private.CoreLib.dll 中的“System.ObjectDisposedException”(“Cannot access a disposed context instance. A common cause of this error is disposing a context instance that was resolved from dependency injection and then later trying to use the same context instance elsewhere in your application. This may occur if you are calling 'Dispose' on the context instance, or wrapping it in a using statement. If you are using dependency injection, you should let the dependency injection container take care of disposing context instances.”) System.ObjectDisposedException

1.18可以复现出来
用的EasyNetQ客户端
消息体
[Queue("DbContextTest", ExchangeName = "DbContextTest")]
public class DbContextTestMessage
{
public string Data { get; set; }
}
消费者
public class DbContextTestMessageConsumer : IConsumeAsync
{
[AutoSubscriberConsumer(SubscriptionId = "Test")]
public async Task ConsumeAsync(DbContextTestMessage message, CancellationToken cancellationToken = default)
{
var xxx = App.ServiceProvider.GetService().xxx; //这里调用存储过程

        await Task.Delay(1000);

        xxx.LogError("DbContextTestMessageConsumer");
    }
}

消息发送接口
[AllowAnonymous]
[HttpPost]
public async Task SendTestMessageAsync()
{
var message = new DbContextTestMessage()
{
Data = ""
};
await _bus.PubSub.PublishAsync(message);
}

每调用一次，数据库连接就会增长一个

我刚刚优化了数据库上下文池和创建数据库上下文的代码：9cb3c00

经过我这边测试，已经没问题。我看看今晚是否发一个版本给您。或者您先拿源码版本测试看看。

按文档的解决方案，解决问题了。非常感谢！

我也更新了1.18.9了