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

Force reconnection when a null message is received #130

Open
mattiekat opened this issue May 20, 2020 · 0 comments
Open

Force reconnection when a null message is received #130

mattiekat opened this issue May 20, 2020 · 0 comments

Comments

@mattiekat
Copy link

I am not fully certain on what grounds a null message occurs, however, I ran across this issue when switching to this library thanks to a test case someone now long gone wrote.

Specifically, it checked to make sure that the system would handle a queue being deleted and recreated. This results in a null message which our old system used as a trigger for reconnecting.

As far as I can tell, there is no valid way to reconnect so I ended up writing await this.connectionWrapper._currentConnection.close() to force a reconnection. This feels fundamentally wrong, but it did fix the test case.

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

No branches or pull requests

1 participant