Websockets timeout ?

[titmael]

Hi,

I've just found a serious problem (I lost lot of hairs today on it).

I use websockets between my java app and the javascript front. The connection is ok, websocket opens et communication's good. But if the front user kill his tab/browser, the websocket isn't clearly closed (the method @OnClose isn't called server side).

So when the server tries to send a message to this user, it's just go somewhere I don't know, no exception raised ...

The workaround I've found is to clearly close the websocket on front side with (only working if browser process isn't hard killed) :

window.onbeforeunload = function(){

        $scope.websocket.onclose = function () {}; // disable onclose handler first

        $scope.websocket.close();

    };

But is there any way to declare a timeout on the websocket ? If the server can't send it's message within X secondes, it raises an exception ?

[rhusar]

How about https://javaee-spec.java.net/nonav/javadocs/javax/websocket/Session.html#setMaxIdleTimeout(long) ?

Set the non-zero number of milliseconds before this session will be closed by the container if it is inactive, ie no messages are either sent or received. A value that is 0 or negative indicates the session will never timeout due to inactivity.

[titmael]

I don't want to close the socket if inactive, I would like to timeout the sentText method on server side