Setting the keep-alive to unlimited reduces rtmpt disconnection rates.

[menelaosbgr]

Pull Request

This PR fixes #1982
Changes proposed in this pull request:
Increase max keep-alive requests to infinite in order to improve disconnection rate.
Refs: bigbluebutton/bigbluebutton#1982

(cherry picked from commit 1427b9b)

[menelaosbgr]

Given that RTMPT creates a massive number of continuous http requests on the RED5 tomcat server, it makes sense to increase this parameter to a very large number (e.g. 50000) or even infinite (-1). RTMPT protocol implementation is very vulnerable and finicky to delays.

Additionally, please see example documentation on specific param: tomcat,websphere .

Tomcat - maxKeepAliveRequests
The maximum number of HTTP requests which can be pipelined until the connection is closed by the server. Setting this attribute to 1 will disable HTTP/1.0 keep-alive, as well as HTTP/1.1 keep-alive and pipelining. Setting this to -1 will allow an unlimited amount of pipelined or keep-alive HTTP requests. If not specified, this attribute is set to 100.

maxKeepAliveRequests of httpOptions

This option specifies the maximum number of persistent requests that are allowed on a single HTTP connection if persistent connections are enabled. A value of -1 means unlimited. This option supports low latency or high throughput applications, and SSL connections for use in situations where building up a new connection can be costly. Here is an example of how you code this option in the server.xml file:

<httpOptions maxKeepAliveRequests="-1" />

Kind Regards,
Chris Georgoulis, cgeorgoulis@gmail.com
Menelaos Bakopoulos, menelaosbgr@gmail.com