[jira] [Commented] (WICKET-4371) Timer problems with Internet Explorer

["Mikko Pukki (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13197822#comment-13197822 ] 

Mikko Pukki commented on WICKET-4371:
-------------------------------------

Hi,
I tried the patch with 1.5.4 and it truly seemed that it helped. Until my colleague pointed out that this happens also on Firefox.
So we tested with 3.6.25, 9.x and 10.x versions. The quickstart seemed to work, but in our real life applications this error still exists (in both, ie and Firefox).
Almost all of our pages are stateful and have some kind of timers to update the content. When changing page through our menu,
maybe once in every 10 to 40 times, timer request from previous page is sent after new page is rendered. This must be some kind of
timing problem? I'll attach a file that contains requests sent from Firefox. It can be viewed with http://www.softwareishard.com/har/viewer/
                
> Timer problems with Internet Explorer
> -------------------------------------
>
>                 Key: WICKET-4371
>                 URL: https://issues.apache.org/jira/browse/WICKET-4371
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.19, 1.5.3, 1.5.4
>         Environment: Jetty/Apache Tomcat & Internet Explorer
>            Reporter: Mikko Pukki
>         Attachments: TimerProblem.zip, WICKET-4371.patch
>
>
> Hi,
> We are encountering problems on all pages that have timers for updating/polling new data.
> It seems that if new page is rendering, timer's request can mess things up. Problem can be
> reproduced with Wicket 1.5.3 and 1.5.4
> An example situation:
> 1) Page (id1) has a timer and user presses link (Request1) that forwards to a new Page (future id2).
> 2) Request is being processed at server and page with id2 is rendered
> 3) While still in render phase timer makes new request to a server
> Timer's request is handled even if there is a new rendered page. Timer's request is now last request
> handled and page that contained timer is last page stored at PageTable. This causes weird problems with
> our applications.
> I'm wondering that why any request that is meant for previous versions of pages are processed?
> In quickstart rendering is slowed down with Thread.sleep, but network latencies can and will create similar problems.
> In the quickstart there is PageB -link. Pressing that invokes this behavior
> There is also custom store in quickstart that provider simple debug logging. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira