Thanks Martin!
https://issues.apache.org/jira/browse/WICKET-6782
will create PR in a moment :)
On Wed, 6 May 2020 at 00:22, Martin Grigorov wrote:
> Hi Maxim,
>
> On Fri, May 1, 2020 at 2:22 PM Maxim Solodovnik
> wrote:
>
> > On Fri, 1 May 2020 at 18:15, Martin Grigorov
> wrote:
> >
> > > Hi
Hi Maxim,
On Fri, May 1, 2020 at 2:22 PM Maxim Solodovnik
wrote:
> 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* 0
Here are some more details on this issue
In our code I'm using IWebSocketConnection.sendMessage(String) method
The call is wrapped with try/catch to correctly handle any exception [1]
The problem is hard to reproduce due to IOException should happen exactly
at time of sendMessage do it's job
(in
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 occurre
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 WebSocketBeha
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 connec
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.
https://github.com/apache/wicket/blob/master/wicket-native-websocket/wicket-native-websocket-javax/src/main/java/org/apache/wicket/protocol/ws
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]