Detect ungraceful client disconnects about play2-sockjs HOT 3 OPEN

Yes, as stated in the link that you posted the only way to detect a broken TCP connection is trying to send some bytes. In SockJSSettings there is an option with which you can tune the heartbeat interval, it serves the purpose but there is an issue.

I tested it on Play 2.5 but it doesn't work, Play just keep sending data without detecting that the other end went away, I reproduced it by writing this simple action that returns a chunked response:

def test = Action {
    val source = 
      Source.tick(200.millis, 200.millis, "tick")
        .map(s => {println(System.currentTimeMillis()); s})
        .watchTermination() { (_, r) =>
          r.onComplete(println)
        }
    Ok.chunked(source)
  }

If you run it and disconnect the cable the source will never ends. Since play2-sockjs relies on the underlying Play implementation there is not much that I can do. I smell a bug here, but before reporting it I want to do further investigation.

from play2-sockjs.

By the way it could be fixed by implementing a ping/pong style heartbeat, but unluckily SockJS protocol does not support it natively, so you need to implement it at higher level.

from play2-sockjs.

I tested it further and it does detect disconnect, but it does after enough data has been transferred, so I guess there is some internal buffer and timeout that control this.

As I said before one simple way to implement it reliably is by sending an ping message and waiting for the pong, if the response doesn't come in time then you detected an unreliable connection.

I'll keep the issue open for further investigations.

from play2-sockjs.