Hi Kevin,

The log confirms that the xhr.html requests are in charge of the difference between the number of connections and sessions.
However in this case the situation does not collapses and we have no messages "Current delay ..." as in recent days.

About the messages like these:

Code:
"Current delay for tasks scheduled on thread pool TLS/SSL HANDSHAKE is x seconds."

"Handshake error on Lightstreamer HTTPS Server: task timed out on ..."
these messages were a direct result of the huge number of HTTPS connection requests queued in the evening of 21 February.

The TLS/SSL handshake is a quite demanding operation that can subtract many resources to the rest of the server.
For this reason, the factory configuration for the <handshake_pool_size> is 1.
If peaks of HTTP connection requests are expected you could raise this number to better cope with the requests. But I do not think it's your case, since it was an abnormal episode that should not be repeated.

Regards,
Giuseppe