Project

General

Profile

Feature #6579

Keep-alive time just for first signal

Added by José Luis Rey almost 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
08/31/2018
Due date:
% Done:

0%

Estimated time:

Description

Hello,

We're using wt server in some customers that use networks monitors to check service avalibity, this tools usually ping a server each minute or half a minute to check if the service is alive.

When using "dedicated-process" this means that each ping will generate a new process consuming a considerable amount of memory, this sessions will not be closed until the the defined timeout is reached.

I beleive that after a session is created, if we don't receive a keep alive, lets say, 5 seconds, the process/session should be close directly.

Controlling first keep-alive/timeout in a different way can helps a lot with this kind of services.

Best regards

J.Rey

Also available in: Atom PDF