Details
Bug
Major
Description
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.
Activity
Does the freeze occur during interaction with UI? Does that interaction contain a long running process of some kind? Any application process on the server that blocks the UI connection for too long should probably be factored so that the the updates are sent back using Ajax Push so that the UI connection is not held too long. With IE and its connection limit, this would manifest in the way described.
i have setup the push-server and it works fine.
after analysing the state befor and after i found differences in the js-variable configuration.
i think the construct is wrong in mode without push-server and it send the request somewhere wrong.
it should be something like
...
connection: {
context:
,
...
please look at the code-snips from the page in the attachment (with and without push-server).
| Field | Original Value | New Value |
|---|---|---|
| Attachment | push-server.txt [ 12017 ] |
| Assignee | Mircea Toma [ mircea.toma ] |
It seems that the JS configuration for the deployment without push-server was cached by the browser. The configuration for 1.8.2 release should look like the one in the deployment with push-server.
hello
it looks like the js configuration is still different but the handling of the configuration changed in 1.8.2
the freeze itself seems to be gone with the new version even without the push server.
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.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Incomplete [ 4 ] |
| Fix Version/s | 1.8.2 [ 10190 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Multiple applications being run?
Multiple windows/tabs pointing at the application(s)?
Push Server being used?
If it's easy for you to do, it might be worthwhile to have a quick run with 1.8.2 to see if any fixes in there help.