[
https://issues.apache.org/jira/browse/TS-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573546#comment-14573546
]
Thomas Jackson commented on TS-3659:
------------------------------------
[~jamespeach] Kinda... let me give some background to the request. Basically
for all the different protos we support they all come down to HTTP/1.1 requests
coming out of ATS. Those requests have limits (max server sessions). Websockets
end up using that same type of connection-- but as a blind tunnel. This means
in the case where you have edge nodes that proxy back to some other location
websockets will (most likely) end up consuming the majority of open sessions.
The concern is that these unused blind tunnel connections (in a failure
condition) could edge out regular HTTP requests that would only tie up the
session for shorter periods of time.
> Add new config to limit maximum number of websocket connections
> ---------------------------------------------------------------
>
> Key: TS-3659
> URL: https://issues.apache.org/jira/browse/TS-3659
> Project: Traffic Server
> Issue Type: Improvement
> Components: Core
> Reporter: Brian Geffon
> Assignee: Brian Geffon
> Fix For: 6.0.0
>
>
> It would be nice to have a config that will limit the maximum number of
> websocket connections.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
