You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Start server, start client, wait for client to exit and observe that only Connected is logged. Issue seems to be that io.jooby.internal.undertow.UndertowWebSocket#onCloseMessage is called, but channel.isOpen() is already false so close handler is not invoked.
The text was updated successfully, but these errors were encountered:
When a client disconnects in an unclean fashion (e.g. process crashes, connection is dropped) the onClose is never called.
Jooby Version: 3.0.1 (with undertow)
Reproduction example:
Server
Client (using
com.squareup.okhttp:okhttp:2.7.5
,com.squareup.okhttp:okhttp-ws:2.7.5
)Start server, start client, wait for client to exit and observe that only Connected is logged. Issue seems to be that
io.jooby.internal.undertow.UndertowWebSocket#onCloseMessage
is called, butchannel.isOpen()
is already false so close handler is not invoked.The text was updated successfully, but these errors were encountered: