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

Calling Drain on a closed connection throws NATSTimeoutException instead of NATSConnectionClosedException #356

Closed
jadurda opened this issue Jan 22, 2020 · 1 comment · Fixed by #359

Comments

@jadurda
Copy link

jadurda commented Jan 22, 2020

Any exceptions that occur during the private drain(int timeout) method gets replaced by a NATSTimeoutException. This is particularly unexpected in the case that Drain is called on a closed connection:

https://github.com/nats-io/nats.net/blob/c50d7f6854a556fbc5d0bae646d147499dc683b9/src/NATS.Client/Conn.cs#L3897-L3939

@ColinSullivan1
Copy link
Member

Good catch - thanks! I'll take a look.

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 a pull request may close this issue.

2 participants