Re: Joda-time dependency

[Martin Makundi]

Just brute force it and we can fine-tune later.

2017-09-14 7:11 GMT+03:00 Maxim Solodovnik :

> Hello Martin,
>
> I tried to continue this work, but it seems I need some information
> before I can proceed
> Could you please tell me What was the goal of these changes?
>
> I would remove joda-time, and use LocalDate, LocalTime instead of Date
> As I can see you are using ZonedDateTime ...
>
>
> On Mon, Sep 11, 2017 at 9:01 PM, Martin Grigorov 
> wrote:
> > Yes, if finished on time!
> > Wicket 7 requires Java 7
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Mon, Sep 11, 2017 at 3:34 PM, Rakesh A 
> > wrote:
> >
> >> Hi,
> >>
> >> Is it going to be for Wicket 8 only ?
> >>
> >> Regards,
> >> Rakesh.A
> >>
> >> --
> >> Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-
> >> f1842947.html
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> >> For additional commands, e-mail: users-h...@wicket.apache.org
> >>
> >>
>
>
>
> --
> WBR
> Maxim aka solomax
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

Re: WebSocket and timeout

[Maxim Solodovnik]

you can add timeout behavior which will send ajax requests
these requests will refresh session

So far this is the only workaround i can propose

On Fri, Sep 15, 2017 at 11:53 PM, Manfred Bergmann
 wrote:
> Hi.
>
> I'm not exactly certain how that helps me, except that the not yet released
> version 7.8.1 fixes something regarding WebSockets. But I don't know if it's
> that.
>
> The thing is, that I have a one page application. Meaning the page itself
> doesn't ever refresh. Only panels are reloaded here and there via Ajax.
> One of those panels uses a WebSocket.
> The WebSocket times out even if I move away from this particular panel.
> After the WebSocket has timed out it's only to possible to really reload the
> page to re-activate it.
>
> So, preferably I'd like to WebSocket to not expire before the session
> expired.
>
>
> Manfred
>
> --
> Sent from: 
> http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WebSocket and timeout

[Manfred Bergmann]

Hi.

I'm not exactly certain how that helps me, except that the not yet released
version 7.8.1 fixes something regarding WebSockets. But I don't know if it's
that.

The thing is, that I have a one page application. Meaning the page itself
doesn't ever refresh. Only panels are reloaded here and there via Ajax.
One of those panels uses a WebSocket.
The WebSocket times out even if I move away from this particular panel.
After the WebSocket has timed out it's only to possible to really reload the
page to re-activate it.

So, preferably I'd like to WebSocket to not expire before the session
expired.


Manfred

--
Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: WebSocket and timeout

[Maxim Solodovnik]

According to tomcat user list web socket activity does not touch session
You can set timeout ping behavior to touch the session

Here is the thread with my question according this
http://markmail.org/thread/g2ao4a4ytc3322b5

On Fri, Sep 15, 2017 at 10:05 PM, Bergmann Manfred
 wrote:
> Hi.
>
> I’m having a problem with WebSocket timeouts.
> One panel (currently) of a page uses a WebSocket to push data and re-render 
> something.
> Leaving the browser untouched the WebSocket will timeout after 5 minutes:
> —-
> [ERROR] 2017-09-15 16:57:46.566 [Scheduler-1197176722] 
> org.apa.wic.pro.ws.jav.WicketEndpoint onError - An error occurred in web 
> socket connection with id : 0:0:0:0:0:0:0:1:8080->0:0:0:0:0:0:0:1:55737
> java.net.SocketTimeoutException: Timeout on Read
> at 
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:592)
>  [websocket-common-9.4.6.v20170531.jar:9.4.6.v20170531]
> at 
> org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:170)
>  [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
> at 
> org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:538)
>  [websocket-common-9.4.6.v20170531.jar:9.4.6.v20170531]
> at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.failed(AbstractConnection.java:285)
>  [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
> at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:140) 
> [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
> at 
> org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:398)
>  [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
> at 
> org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166) 
> [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
> —-
>
> Now, what exactly is responsible for this timeout. And how can that be 
> adjusted?
>
>
>
> Regards,
> Manfred
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>



-- 
WBR
Maxim aka solomax

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

WebSocket and timeout

[Bergmann Manfred]

Hi.

I’m having a problem with WebSocket timeouts.
One panel (currently) of a page uses a WebSocket to push data and re-render 
something.
Leaving the browser untouched the WebSocket will timeout after 5 minutes:
—-
[ERROR] 2017-09-15 16:57:46.566 [Scheduler-1197176722] 
org.apa.wic.pro.ws.jav.WicketEndpoint onError - An error occurred in web socket 
connection with id : 0:0:0:0:0:0:0:1:8080->0:0:0:0:0:0:0:1:55737
java.net.SocketTimeoutException: Timeout on Read
at 
org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onReadTimeout(AbstractWebSocketConnection.java:592)
 [websocket-common-9.4.6.v20170531.jar:9.4.6.v20170531]
at 
org.eclipse.jetty.io.AbstractConnection.onFillInterestedFailed(AbstractConnection.java:170)
 [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
at 
org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillInterestedFailed(AbstractWebSocketConnection.java:538)
 [websocket-common-9.4.6.v20170531.jar:9.4.6.v20170531]
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.failed(AbstractConnection.java:285)
 [jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:140) 
[jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
at 
org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:398) 
[jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
at 
org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166) 
[jetty-io-9.4.6.v20170531.jar:9.4.6.v20170531]
—-

Now, what exactly is responsible for this timeout. And how can that be adjusted?



Regards,
Manfred


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org