On Fri, 1 May 2020 at 18:15, Martin Grigorov wrote:
> Hi Maxim,
>
> On Fri, May 1, 2020 at 1:31 PM Maxim Solodovnik
> wrote:
>
> > Hello Martin,
> >
> > WicketEndpoint#onError is being called
> > "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100
> > [EventExec-e2-t9] - An error
Hi Maxim,
On Fri, May 1, 2020 at 1:31 PM Maxim Solodovnik
wrote:
> Hello Martin,
>
> WicketEndpoint#onError is being called
> "*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100
> [EventExec-e2-t9] - An error occurred in web socket connection with id :
> 10"
>
> The problem
Hello Martin,
WicketEndpoint#onError is being called
"*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100
[EventExec-e2-t9] - An error occurred in web socket connection with id : 10"
The problem WebSocketBehavior#onError is not being called
So my application doesn't get notified the
Hi Maxim,
If WicketEndpoint#onError() [1] is not called then probably there is a bug
in Tomcat.
I suggest you to post this question at Tomcat's users@.
1.
Hello,
I'm having weird situation: WebSocket connection is closed on page reload,
but none of my onClose/onError/onAbort handlers are being called
I have changed wicket version to latest SNAPSHOT and got some debug logs:
*ERROR* 05-01 16:10:21.740 o.a.w.p.w.j.WicketEndpoint:100
[EventExec-e2-t9]
