Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Message Consumers stop after RabbitMq restart
See original GitHub issueIs this a bug report?
Yes
Can you also reproduce the problem with the latest version?
Yes, MassTransit 5.2.3.
Environment
- Operating system: Windows 10 Pro
- Visual Studio version: 2017
- Dotnet version: Core 2, Net Framework 4.7.1.
- Language version: C# 7.1 or higher
- RabbitMq version: 3.7.3
Steps to Reproduce
See repository on https://github.com/jlandheer/MassTransitReconnectTest
Basically create a client with a static async Task Main(string[] args) startup method and start the receiving bus with await bus.StartAsync();. Stop the RabbitMq service and start it again. The receiver will not receive messages after restart.
When using the synchronous version there is no problem.
Expected Behavior
Client should continue to receive messages after service restart.
Actual Behavior
Client stops receiving messages after service restart.
Reproducible Demo
See repository on https://github.com/jlandheer/MassTransitReconnectTest
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Wow, good catch. Changed it to
await Task.Run(() => Console.ReadKey());, and as the French say: voilà!I had the same problem. Thanks for the tip, I wouldn’t have found the solution without you!