You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Ingram Chen (JIRA)" <ji...@apache.org> on 2007/06/21 19:15:26 UTC

[jira] Created: (WICKET-683) Fast multiple clicks cause page expiration

Fast multiple clicks cause page expiration
------------------------------------------

                 Key: WICKET-683
                 URL: https://issues.apache.org/jira/browse/WICKET-683
             Project: Wicket
          Issue Type: Bug
          Components: wicket
    Affects Versions: 1.2.6
         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
            Reporter: Ingram Chen


It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:

First:

(1) make a link that require 5 seconds to process.
(2) quick click that link >3 times, after 5 seconds, go to page B
(3) do any thing on page B cause expire.

Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.

attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
(note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)

2nd:

step 1: link to homepage    
           url is http://localhost:8081/quickstart/app

step 2: "double click" link on homepage, go to 2nd instance of page B
           url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
           (double click create two instances of page B)

step 3: use browser back button go back to first instance of page B
           url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::

step 4: do anything on first instance of page B will cause expiration.
          
Ideally 1st instance of page B should in pageMap but it seems got lost. 

see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507149 ] 

Eelco Hillenius commented on WICKET-683:
----------------------------------------

Ok, so at least we pinned down that HttpSessionStore and the kind of pagemaps it uses is the problem.

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6, 1.3.0-beta1
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Ingram Chen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ingram Chen updated WICKET-683:
-------------------------------

    Attachment: quickstart-click3times.tar.gz

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507134 ] 

Eelco Hillenius commented on WICKET-683:
----------------------------------------

One big difference in 1.3 is that we set the SecondLevelCacheSessionStore as the default session, whereas in 1.2 that store didn't exist yet, and we use the HttpSessionStore. You could try to test 1.3 for this problem with the HttpSessionStore by putting this in your application class:

/**
 * @see WebApplication#newSessionStore()
 */
@Override
protected ISessionStore newSessionStore() {
  return new HttpSessionStore(this);
}

If you can reproduce the problem then, we'll know it has to do with this session store and the page map algorithm it uses.

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Ingram Chen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507126 ] 

Ingram Chen commented on WICKET-683:
------------------------------------

I play above two test with 1.3 examples, and it is not reproducible.
Fast multiple clicks won't create multiple instance of target page
( the url remain http://localhost:8081/quickstart/app/?wicket:interface=:1::  even with 3,4...etc clicks )
So this only affects wicket 1.2 branch.

The question is where is the magic in 1.3 ? 
We can't upgrade to 1.3 now, but I would like to patch 1.2 by ourself.



> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Ingram Chen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507146 ] 

Ingram Chen commented on WICKET-683:
------------------------------------

I test 1.3 locally and yes, there is no expiration when using SecondLevelCacheSessionStore. 
After switching to HttpSessionStore, the behavior is the same as 1.2.x

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507463 ] 

Matej Knopp commented on WICKET-683:
------------------------------------

I believe this actually a "feature" of AccessStackPageMap. We've talked about this a lot with johan, and I'm affraid there really is no good solution (apart from using 2nd level cache session store). Anyway, maybe it's time to reconsider the behavior of dropping pages from accessstackpagemap. 

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6, 1.3.0-beta1
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Matej Knopp (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp reassigned WICKET-683:
----------------------------------

    Assignee: Johan Compagner

It's your baby, deal with it ;-)) 

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6, 1.3.0-beta1
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>            Assignee: Johan Compagner
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Eelco Hillenius (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eelco Hillenius updated WICKET-683:
-----------------------------------

    Affects Version/s: 1.3.0-beta1

Also relevant for 1.3

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6, 1.3.0-beta1
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (WICKET-683) Fast multiple clicks cause page expiration

Posted by "Ingram Chen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WICKET-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ingram Chen updated WICKET-683:
-------------------------------

    Attachment: quickstart-2clickback.tar.gz

> Fast multiple clicks cause page expiration
> ------------------------------------------
>
>                 Key: WICKET-683
>                 URL: https://issues.apache.org/jira/browse/WICKET-683
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.2.6
>         Environment: linux 2.6.20, firefox 2.0.4, dual core, sun jdk6
>            Reporter: Ingram Chen
>         Attachments: quickstart-2clickback.tar.gz, quickstart-click3times.tar.gz
>
>
> It has been found multiple clicks may cause page expiration. there are known two ways to reproduce such problem:
> First:
> (1) make a link that require 5 seconds to process.
> (2) quick click that link >3 times, after 5 seconds, go to page B
> (3) do any thing on page B cause expire.
> Mulitple clicks is quite normal under slow network. The user may click link several times because web site is not responsive.
> attachement quickstart-click3times.tar.gz is quickstart to reproduce this problem.
> (note LeastRecentlyAccessedEvictionStrategy(100) up to 100 access to eliminate eviction issues)
> 2nd:
> step 1: link to homepage    
>            url is http://localhost:8081/quickstart/app
> step 2: "double click" link on homepage, go to 2nd instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:2::
>            (double click create two instances of page B)
> step 3: use browser back button go back to first instance of page B
>            url becomes http://localhost:8081/quickstart/app/?wicket:interface=:1 ::
> step 4: do anything on first instance of page B will cause expiration.
>           
> Ideally 1st instance of page B should in pageMap but it seems got lost. 
> see attachement quickstart-2clickback.tar.gz

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.