Unexpected disconnections - How to determine who terminated?

[aychedee]

Hi again,

We have a large number of unexpected disconnections. The on_close method only receives the session. Is there any way of using the on_close method to figure out who initiated the close? Whether the client or server.

Cheers

aychedee

[mrjoes]

Right now there's no way to figure it out.

I will think how to add this without changing existing api (thinking of self.session.close_reason).

[aychedee]

Thanks Serge!

[mrjoes]

I will keep this open, so I won't forget about it.

[mcilfone]

Hi Mr Joes,
I'm dealing with an unexpected SockJS disconnection.
There is no call to my connection.on_close function.
And there is no reason, even after calling the session get_on_close_reason method.
How can I deal with it?

I'm using sockjs-tornado==1.0.1 with tornado==4.0.2 and sockjs.js==0.3.4

Thanks