wicket-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Grigorov <mgrigo...@apache.org>
Subject Re: WebSocketBehavior::onClose is not being called in case of network connection is lost
Date Sat, 09 Feb 2019 21:26:32 GMT
Hi Maxim,


On Sat, Feb 9, 2019 at 6:51 PM Maxim Solodovnik <solomax666@gmail.com>
wrote:

> Hello All,
>
> I just have noticed WebSocketBehavior::onClose/onError is not being
> called in case of network connection is lost (Tested in Tomcat and
> Jetty)
>

I.e. Tomcat/Jetty do not call javax.websocket.Session#close() at all ?
Wicket just provides an abstraction over JSR356 WebSocket APIs. Wicket
doesn't deal with network calls and/or http/websocket sessions. If the
container notifies Wicket then Wicket cleans up internallly and notifies
the application.


>
> It also seems invalid IWebSocketConnection is staying in the registry
>
> Is this known issue/behavior?
> Shall Wicket code be updated to drop such invalid connections and call
> onClose() or onError() ?
>
> --
> WBR
> Maxim aka solomax
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message