-
Notifications
You must be signed in to change notification settings - Fork 19
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
Connection Idle timeout feature for TCP Adaptor #1145
Labels
enhancement
New feature or request
Comments
I'm thinking that we probably only need to add this to the tcpListener since it doesn't matter which side of the connection is closed. |
Leaving as draft for the moment. As written it will require a fix to #1155 since this patch requires a large number of simultaneously active timers. |
Closing this since the associated PR is closed. Reopen if necessary |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal: Add the ability to detect and close idle TCP connections.
Add a new configuration attribute to the tcpConnector and tcpListener records - idleTimeoutSecs. This value sets a limit to the time a TCP connection can remain idle - i.e. passing no data - before the router will proactively close the connection. The value is expressed in seconds. A value of zero disables the idle timeout (the connection will not be closed).
If configured on both ends of the connection (both the tcpConnector and the tcpConnection) the lowest value takes precedence.
The text was updated successfully, but these errors were encountered: