Number of active tunnels are accumulated gradually

Hi Sharon,

This is a timeout issue. While the server is under load, tunnel communication might take longer than 10 seconds and a timeout occurred. In that event, server still keeps the tunnel session in the Active list while that's already disconnected.

Edge logs

{"level":"FORCE","timestamp":"2019-12-17T11:48:00,664","origin":"SDK","content":"TUNNEL CREATED. Entity: IPU_TEST, tid: 71d70bae-2994-4ebe-a971-efa2362f3dfb, target: 127.0.0.1:5900"}
{"level":"FORCE","timestamp":"2019-12-17T11:48:10,466","origin":"SDK","content":"TUNNEL STARTED. Entity: IPU_TEST, tid: 71d70bae-2994-4ebe-a971-efa2362f3dfb, target: 127.0.0.1:5900"}
{"level":"FORCE","timestamp":"2019-12-17T11:48:11,406","origin":"SDK","content":"TUNNEL ENDED. Entity: IPU_TEST, Peer: TEST, tid: 71d70bae-2994-4ebe-a971-efa2362f3dfb, target: 127.0.0.1:5900"} 

and server logs

2019-12-17 11:48:11.556-0600 [L: ERROR] [O: c.t.w.t.WSTunnelServer] [I: ] [U: ] [S: ] [T: http-nio-0.0.0.0-443-exec-820] Error occurred in web socket: An existing connection was forcibly closed by the remote host 

I bet that when the local socket read timeout (Default is 10 seconds) occurs, the tunnel is immediately ended. While it should give a few chances before terminating the tunnel. The current implementation is causing a lot of issues while the server is under load.

My Bests,

Hung Tran