You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Maxim Solodovnik <so...@gmail.com> on 2017/09/09 13:06:40 UTC
Session timeout and ajax timer behavior
Hello All,
I'm observing weird behavior:
AbstractAjaxTimerBehavior(Duration.seconds(30)) is set in my application.
It is being regularly called (according to debugger and log messages)
I set it up to prevent Tomcat session timeout [1]
Surprisingly I got session timeout and see no http requests in Browser
Dev Tools (Network tab)
Can you please tell me how is this possible?
[1] http://tomcat.10.x6.nabble.com/Session-timeout-despite-user-activity-websockets-on-Tomcat-8-5-16-td5066265.html
--
WBR
Maxim aka solomax
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Session timeout and ajax timer behavior
Posted by Maxim Solodovnik <so...@gmail.com>.
Yep
works as expected with 8.0.0-SNAPSHOT
Thanks a lot!
On Sun, Sep 10, 2017 at 2:11 PM, Martin Grigorov <mg...@apache.org> wrote:
> Hi Maxim,
>
> Try with 8.0.0-SNAPSHOT.
> I think this is the same issue as the one that requires 7.8.1.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Sat, Sep 9, 2017 at 3:35 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
>
>> The issue seems to be Chrome specific, I can see requests in FF and
>> session is not expired in FF ....
>>
>> On Sat, Sep 9, 2017 at 8:06 PM, Maxim Solodovnik <so...@gmail.com>
>> wrote:
>> > Hello All,
>> >
>> > I'm observing weird behavior:
>> >
>> > AbstractAjaxTimerBehavior(Duration.seconds(30)) is set in my
>> application.
>> > It is being regularly called (according to debugger and log messages)
>> > I set it up to prevent Tomcat session timeout [1]
>> >
>> > Surprisingly I got session timeout and see no http requests in Browser
>> > Dev Tools (Network tab)
>> >
>> > Can you please tell me how is this possible?
>> >
>> > [1] http://tomcat.10.x6.nabble.com/Session-timeout-despite-
>> user-activity-websockets-on-Tomcat-8-5-16-td5066265.html
>> >
>> > --
>> > WBR
>> > Maxim aka solomax
>>
>>
>>
>> --
>> WBR
>> Maxim aka solomax
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
--
WBR
Maxim aka solomax
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Session timeout and ajax timer behavior
Posted by Martin Grigorov <mg...@apache.org>.
Hi Maxim,
Try with 8.0.0-SNAPSHOT.
I think this is the same issue as the one that requires 7.8.1.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Sat, Sep 9, 2017 at 3:35 PM, Maxim Solodovnik <so...@gmail.com>
wrote:
> The issue seems to be Chrome specific, I can see requests in FF and
> session is not expired in FF ....
>
> On Sat, Sep 9, 2017 at 8:06 PM, Maxim Solodovnik <so...@gmail.com>
> wrote:
> > Hello All,
> >
> > I'm observing weird behavior:
> >
> > AbstractAjaxTimerBehavior(Duration.seconds(30)) is set in my
> application.
> > It is being regularly called (according to debugger and log messages)
> > I set it up to prevent Tomcat session timeout [1]
> >
> > Surprisingly I got session timeout and see no http requests in Browser
> > Dev Tools (Network tab)
> >
> > Can you please tell me how is this possible?
> >
> > [1] http://tomcat.10.x6.nabble.com/Session-timeout-despite-
> user-activity-websockets-on-Tomcat-8-5-16-td5066265.html
> >
> > --
> > WBR
> > Maxim aka solomax
>
>
>
> --
> WBR
> Maxim aka solomax
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Session timeout and ajax timer behavior
Posted by Maxim Solodovnik <so...@gmail.com>.
The issue seems to be Chrome specific, I can see requests in FF and
session is not expired in FF ....
On Sat, Sep 9, 2017 at 8:06 PM, Maxim Solodovnik <so...@gmail.com> wrote:
> Hello All,
>
> I'm observing weird behavior:
>
> AbstractAjaxTimerBehavior(Duration.seconds(30)) is set in my application.
> It is being regularly called (according to debugger and log messages)
> I set it up to prevent Tomcat session timeout [1]
>
> Surprisingly I got session timeout and see no http requests in Browser
> Dev Tools (Network tab)
>
> Can you please tell me how is this possible?
>
> [1] http://tomcat.10.x6.nabble.com/Session-timeout-despite-user-activity-websockets-on-Tomcat-8-5-16-td5066265.html
>
> --
> WBR
> Maxim aka solomax
--
WBR
Maxim aka solomax
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org