java.io.EOFException is thrown from Flow.collect when trying to send a Ping

Ktor Version and Engine Used (client or server and name) Ktor 1.3.2 client, ktor-client-okhttp (on top of ktor-client-core and ktor-client-websockets)

Describe the bug java.io.EOFException is thrown from Flow.collect when trying to send a Ping message

To Reproduce

1. client.wss with a block like this:

{
  incoming.consumeAsFlow()
    .collect { frame ->
      if (frame.isHello) {
        GlobalScope.launch { 
          delay(500L)
          send(Frame.Ping(ByteArray(0)))
        }
      } else {
        // Normal frame processing here.
      }
    }
}

Expected behavior Ping is sent, server responds with Pong.

It’s entirely possible I’m doing something wrong but I can’t see what. This is reproducible 100% of the time. Stacktrace:

[dmitrievanthony]

Hi @edenman, well the only thing I can recommend you is to try CIO out. Is does support manual Ping/Pong processing using RawWebSockets.

And just to fix the status, speaking about OkHttp I see here several inconveniences. Firstly, when we send a frame we don’t get an exception immediately. Send operation is performed asynchronously and we are able to get an exception only when try to send something again. Secondly, OkHttp provides it’s own Ping/Pong mechanism which is not properly integrated with Ktor infrastructure so far.

I can nothing to suggest you but try CIO, so I’ll close the issue. If you have any ideas or suggestions feel free to reopen it.

[techygrrrl]

OkHttp provides it’s own Ping/Pong mechanism which is not properly integrated with Ktor infrastructure so far.

I can nothing to suggest you but try CIO, so I’ll close the issue.

I was experiencing the java.io.EOFException error too and suspected it could be related to pinging while collecting a flow for an extended period of time. Switching to the CIO engine from the OkHttp engine fixed the issue, thanks!