MassTransit (5.0.0) does not reconnect after broker restart (RabbitMq)

[castroal]

Is this a bug report?

Yes

Can you also reproduce the problem with the lastest version?

Yes, the old one (4.0.1) works fine.

Environment

1. Operating system: Windows or Linux
2. Visual Studio version: vscode latest
3. Dotnet version: dotnet core2

Steps to Reproduce

In a RPC scenario when the connection to RabbitMq is lost or the broker is restarted, messages do not get delivered anymore.

1. Create a "server" app with a message consumer
2. Create a "client" app that send messages in loop using bus.CreatePublishRequestClient
3. After the first messages are received, restart the broker

Expected Behavior

The connection from both sides (server and client) should be restored and messages should start to get sent and received again.

Actual Behavior

From the RabbitMq management UI it seems that the connection is restored but messages do not get sent nor received.

Reproducible Demo

https://github.com/castroal/MassTransitTest

1) start the server app
2) start the client app
3) wait for a few messages to be received and restart the broker

[castroal]

That was fast! It seems to work correctly now with the 5.0.0.1485-develop.
Thanks!

[phatboyg]

Good to know. With a reproducible test it doesn't take long to figure out. Thanks for that!

[phatboyg]

I'll release this after the weekend.