Details
Description
IE browser has by default a connection limitation of 2 connections at time.
The push mechanism (long pooling) already blocks one of these lines while the other one is often reserved for the regular communication.
This invokes a freeze of the browser (also the window itself).
After a while (like timeout of the connection) the browser retrieves a response and the user can work again.
With FF no problem happens (no connection limitation).
I have found an ugly workaround by setting in the registry the maximal connection limitation on 16.
The problem seems to disappear. But I can't tell our customer to do that hack.
If I set ...
<context-param>
<param-name>com.icesoft.faces.synchronousUpdate</param-name>
<param-value>true</param-value>
</context-param>
... it works fine.
The push mechanism (long pooling) already blocks one of these lines while the other one is often reserved for the regular communication.
This invokes a freeze of the browser (also the window itself).
After a while (like timeout of the connection) the browser retrieves a response and the user can work again.
With FF no problem happens (no connection limitation).
I have found an ugly workaround by setting in the registry the maximal connection limitation on 16.
The problem seems to disappear. But I can't tell our customer to do that hack.
If I set ...
<context-param>
<param-name>com.icesoft.faces.synchronousUpdate</param-name>
<param-value>true</param-value>
</context-param>
... it works fine.
This issue never showed up in our tests. Even if this is used to be real issue in 1.8.1 it seems to be gone in 1.8.2. Closing this issue for now.