Hi Kevin,
Please note that a new connection does not always mean new client. Sometimes, especially for no webscoket case, clients already connected may require a new connection (for a rebind, or a polling request or a new subscription).
Thus limiting the number of connections can affect the proper functioning of sessions also already established.
The parameters that protect the server from your critical situation are:
[SYNTAX=XML] <server_pool_max_queue>100</server_pool_max_queue>
<handshake_pool_max_queue>100</handshake_pool_max_queue>[/SYNTAX]
and in your specific case it seems that the second might work.
However, for a typical DoS attack scenario, we expect that the firewall should actually apply the necessary countermeasures.
It seems strange to me that it might be a bug in the client side, since the huge difference between the number of sessions and connections. Also because the browser typically limit by itself the number of connections to the same URL.
Please, if the server log of the Saturday episode is available send us it at
support@lightstreamer.com. We will check it in search of clues.
