The problem occurs under the following conditions:
1. A new browser session is started
2. A second browser window that uses the webservice.htc is
created via window.open or target="_new" from the above
parent browser window.
3. The new window is closed quickly by the user while the
webservice is performing requests.
4. The user tries to open another window from the parent
browser window. This causes the new window to hang and can
only be fixed by destroying the whole IE session.
We have tried:
Modifying the behaviour such that when the container
window is closed the webservice.htc code iterates through
its XMLHTTP collection and calls the 'abort' method on
each object. Finally the code cycles through a secobnd
time and sets them to 'null'. We have found that if we
program in a delay after the objects are set to null then
the problem is cured. Unfortunately this work around is
unacceptable as windows take to long to close.
We would appreciate any help anyone can give us on this
matter...
.
I used to work on a system (at Enron!!!) that tried to use
it's own simple XML messaging between browser & server
using the XMLHTTP object.
We got the idea from some MSDN article or something.
Could never figure out how to solve it...
>..
>
>
>.
>
Refer to
http://support.microsoft.com/default.aspx?scid=kb;
[LN];Q183110
This article describes the server connection limit which
is by design. There are also some registry settings
described there that you can tweak to allow more
connections to the server which will stop the browser
locking up while the hung http connections time out.
Hope this helps
Peter
>..
>
>
>.
>