Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possibly fix system staying dead if RabbitMQ was temporary unavailable #89

Merged
merged 2 commits into from
Nov 18, 2021

Conversation

zlepper
Copy link
Contributor

@zlepper zlepper commented Nov 17, 2021

Fixes #88

This does instead cause some null references immediately after, as some of the workers apparently try to access the consumer between it being disposed and set to null. I'm not entirely sure to fix that without causing even more issue. The NullReferenceException issues are also temporary, and the normal retrying will resolve it.
Fixed


Rebus is MIT-licensed. The code submitted in this pull request needs to carry the MIT license too. By leaving this text in, I hereby acknowledge that the code submitted in the pull request has the MIT license and can be merged with the Rebus codebase.

@mookid8000 mookid8000 merged commit 2d085e9 into rebus-org:master Nov 18, 2021
@mookid8000
Copy link
Member

Cool! It's out as Rebus.RabbitMq 7.3.2-b02 on NuGet.org now 🙂

Could you report back in here how it goes? If it works, then I'll release it as a properly versioned package.

@zlepper
Copy link
Contributor Author

zlepper commented Nov 18, 2021

I did already make an internal build and published to our private Nuget package, and that does seem to resolve the issue. :)

@mookid8000
Copy link
Member

OK cool, I'll just go ahead and push it as 7.3.2 now then 🙂

@mookid8000
Copy link
Member

Rebus.RabbitMq 7.3.2 is on NuGet.org now! (or it will be, when their index is updated.... 😁 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Channel stays closed after connection has died
2 participants