Cannot connect to RMQ after update to 7.8.0. about easynetq

[liven-maksim-infotecs]

I've just given it a try with RMQ version 3.13.3 and behaviour is the same.

[Pliner]

Hi @liven-maksim-infotecs,

Without a minimal example which reproduces the issue, we are not able to proceed further. The following works as expected:

docker run -d --name some-rabbit -p 5672:5672 -p 5673:5673 -p 15672:15672 rabbitmq:3.13-management

using EasyNetQ;
using Microsoft.Extensions.DependencyInjection;

var serviceCollection = new ServiceCollection();
serviceCollection.RegisterEasyNetQ("host=localhost", c => c.EnableNewtonsoftJson());
var buildServiceProvider = serviceCollection.BuildServiceProvider();

var bus = buildServiceProvider.GetRequiredService<IAdvancedBus>();

await bus.QueueDeclareAsync("test");

[liven-maksim-infotecs]

I've tried to create sample with service and rmq in docker compose but couldn't reproduce this bug.

BUT I could figure out the reason. I found out that configuration factory isn't called because it's registred with TryRegister() and there was singletone registraion in container already.

That was the reason why SetDefaultProperties() wasn't called.

[liven-maksim-infotecs]

I've created asp.net project with DI with sample.

https://github.com/liven-maksim-infotecs/easynetq-chrush-test

If you start an application via docker compose, it crushes.

[zidad]

Many thanks for the example, I will look into it, but it is supposed to not override any existing registrations so it can be customized by the user.

[liven-maksim-infotecs]

so it can be customized by the user

But if user has already registred config, SetDefaultProperties() will never be called

[MaxLevs]

Should issue be opened again?

[zidad]

That would be fine by me

[MaxLevs]

That would be fine by me

Do you have the ability to reopen as a member or should we mention someone who has?