RE: Dwr 2.0.3, reverseAjaxEnabled and IE6

Some parts of this message have been removed. Learn more about Nabble's security policy.

---

From: Thomas Manson [mailto:dev.mansonthomas@...]
Sent: den 27 mars 2008 14:38
To: users@...
Subject: Re: [dwr-user] Dwr 2.0.3, reverseAjaxEnabled and IE6

Ok Mike,

 

 I'll test the 2.0.4 when it will be out !

 

Thanks,

Thomas.

 

On 3/27/08, Mike Wilson <mikewse@...> wrote:

Hi Thomas,

 

There are variations to what happens under different circumstances with this IE bug. Here is an attempt to summarize the bug pattern:

- The client code sends an XHR request to the server.

- The user leaves the page before the response arrives.

- IE will wait for the response even though the page is gone, occupying the connection.

- If the response is returned in chunked mode (always used by polls) AND the owning window has been closed, then the socket will become a zombie socket forever occupying the connection in CLOSE_WAIT state. Otherwise it will be returned to the browser pool.

 

It sounds like you are staying in the same window and thus would just experience the delay until the "old" reverse ajax connection is released.

 

I have fixed the problem by aborting all ongoing XHR:s at page unload, and I'll check in the fix as soon as SVN becomes available.

 

Best regards

Mike

---

From: Thomas Manson [mailto:dev.mansonthomas@...]
Sent: den 27 mars 2008 13:44
To: users@...
Subject: Re: [dwr-user] Dwr 2.0.3, reverseAjaxEnabled and IE6

 

Hi Mike,

 

 I was a bit busy lately ;)

 

 I've just made the test with TcpView, only One IE launched.

 

 When connected, I've a UDP connection, and 2 TCP ESTABLISHED.

 

 When I click the first time, the action is executed normally.

 

 The second time it takes lot of time.

 

  When I check TcpView, I don't see any connection in CLOSE_WAIT mode.

  But I notice that the browser display the next page just after one of the two established connection is closed and replace by another connection. (the reverse ajax connection ?)

 

Thomas.

 

On 3/17/08, Mike Wilson <mikewse@...> wrote:

> I just tried with the latest CVS (Branch_2_0 branch from java.net)
> with no success: IE gets those CLOSE_WAIT connections forever after
> closing the popup window.

That sounds reasonable as I haven't checked it in yet ;-)
I'm working on the fix and will report back in this discussion thread
(and JIRA) when it is available in CVS.

Best regards
Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...