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

[azeventhubs] Using a client that's been closed has undesirable behavior #22902

Open

richardpark-msft opened this issue May 15, 2024 · 0 comments

Assignees

Labels

Client Event Hubs

Milestone

Member

richardpark-msft commented May 15, 2024

I noticed this while working with a Processor sample. There are a couple of problems I want to tackle as part of this:

Using a client that's been closed doesn't return an error in all cases. In particular, calling GetEventHubProperties() can bypass the "open" check for the client.
When stopping a Processor the individual clients can return an errorString("client has closed") which is actually okay and expected. We should return a new ErrorCode for that so people can ignore it cleanly.

richardpark-msft added Event Hubs Client labels

richardpark-msft added this to the 2024-07 milestone

richardpark-msft self-assigned this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment