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

Expose additional idle timeout configuration in ConnectionOptions #22674

Closed
jsquire opened this issue Jul 15, 2021 · 0 comments
Closed

Expose additional idle timeout configuration in ConnectionOptions #22674

jsquire opened this issue Jul 15, 2021 · 0 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Milestone

Comments

@jsquire
Copy link
Member

jsquire commented Jul 15, 2021

Summary

For some scenarios sensitive to latency or when activity happens in spikes, the default idle timeout of the network stream is not adequate. To address, the connection idle time should be exposed as part of the set of ConnectionOptions used to control the AMQP transport configuration.

Scope of Work

  • The ConnectionOptions will be extended to expose an option for "ConnectionIdleTimeout", with a default value of 60 seconds.

  • The ConnectionIdleTimeout is passed to the AmpqConnectionScope and used for the IdleTimeout when creating the AmqpConnectionSettings that configure all Event Hubs connections. (example)

Success Criteria

  • The enhancements detailed in the scope have been implemented.

  • The tests necessary for its validation have been created or adjusted and pass reliably.

  • The existing test suite continues to pass and produce deterministic results.

@jsquire jsquire added Event Hubs Client This issue points to a problem in the data-plane of the library. labels Jul 15, 2021
@jsquire jsquire added this to the [2021] August milestone Jul 15, 2021
@jsquire jsquire self-assigned this Jul 15, 2021
@jsquire jsquire closed this as completed Jul 16, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

1 participant