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.

Sign up for GitHub

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

Jump to bottom

Poor error message for Connection Refused #88

Open
andrew-stevenson-sociomantic opened this issue Jul 3, 2019 · 1 comment
Open

Poor error message for Connection Refused #88

andrew-stevenson-sociomantic opened this issue Jul 3, 2019 · 1 comment

Comments

@andrew-stevenson-sociomantic
Copy link
Contributor

If a DMQ node is down the error available in the ConnNotification object passed to the connection notifier callback is ConnectProtocol: finalized. I would have hoped for something along the lines of Connection refused to enable debugging of the problem. I'm not sure finalized will mean much to most users.
@andrew-stevenson-sociomantic
Copy link
Contributor Author

It turns out ConnectProtocol: finalized is also the message given for a TCP level time out. The same message for different errors makes troubleshooting even more awkward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andrew-stevenson-sociomantic