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

Missing heart beat closing does not raise the correct notification #362

Open
Gsantomaggio opened this issue Nov 22, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@Gsantomaggio
Copy link
Member

Gsantomaggio commented Nov 22, 2024

Describe the bug

The close notification is incorrect when the client is closed due to a missing heartbeat.
So the client can't be reconnected. The client should consider the missing heartbeat as an error.

Reproduction steps

It should be enough to do the same: rabbitmq/rabbitmq-stream-dotnet-client#393

Expected behavior

Raise the socket closed error so the client can reconnect.

Additional context

No response

@Gsantomaggio Gsantomaggio added the bug Something isn't working label Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant