Connection retry for the transport

Architecture & Design
,
1

Sometimes we have specific problem that causes brokerunreachable exception when we trying to start endpoint

_endpoint = await startableEndpoint.Start(_serviceProvider);

So i searched a lot but found only one post about transport retry in this topic and answer suggested in topic looks like just retrying the “Start phase”.

someLoop() {

...

_endpoint = await startableEndpoint.Start(_serviceProvider);

...


}

And actually this works fine but when my endpoint finally starts i got warnings in logs

(n retries makes n logs)

 A duplicate diagnostic entry was renamed from Hosting to Hosting-5.
15 Jun 2026 13:30:17.372
 A duplicate diagnostic entry was renamed from Hosting to Hosting-5.
15 Jun 2026 13:30:17.372
 A duplicate diagnostic entry was renamed from Hosting to Hosting-4.
15 Jun 2026 13:30:17.371
 A duplicate diagnostic entry was renamed from Hosting to Hosting-4.
15 Jun 2026 13:30:17.370
 A duplicate diagnostic entry was renamed from Hosting to Hosting-3.
15 Jun 2026 13:30:17.369
 A duplicate diagnostic entry was renamed from Hosting to Hosting-3.
15 Jun 2026 13:30:17.368
 A duplicate diagnostic entry was renamed from Hosting to Hosting-2.
15 Jun 2026 13:30:17.367
 A duplicate diagnostic entry was renamed from Hosting to Hosting-2.

Should i worry about this warnings? Because right now i didnt find way to find/fix problem that causes this

2

Hi!
Those warnings are just a part of the startup diagnostics. Because your loop is trying to start the endpoint until it succeeds, it calls Start() multiple times, so there are multiple diagnostics entries.

The warnings are nothing to worry about, but the fact that you need to run it in a loop indicates that the broker is not available when your endpoint is starting. This might be worth looking into.

Regards,
Bartek

1 Like