Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0
-
Fix Version/s: 3.3
-
Labels:None
-
Environment:ICEfaces 3.2.0.A 12192012
-
Assignee Priority:P1
-
ICEsoft Forum Reference:
-
Salesforce Case Reference:
-
Workaround Exists:Yes
-
Workaround Description:Use session scoped beans
Description
Comments from the customer who is seeing this issue:
"We are seeing cases of two user sessions sharing the same window id and the corresponding window scope map are shared too. The main problem is in WindowScopeManager, which maintains a static variable UnusedScopeMap. This variable is shared across multiple sessions"
"We are seeing cases of two user sessions sharing the same window id and the corresponding window scope map are shared too. The main problem is in WindowScopeManager, which maintains a static variable UnusedScopeMap. This variable is shared across multiple sessions"
I managed to reproduce the issue using the "scopes" test application. The trick was to change the org.icefaces.windowScopeExpiration value to 3000ms. The steps to reproduce are:
1) Load http://localhost:8080/scopes/window-scope-A.jsf in first browser.
2) Load http://localhost:8080/scopes/window-scope-A.jsf in second browser.
3) Restart web server.
4) Reload http://localhost:8080/scopes/window-scope-A.jsf in first browser.
5) Increment counter to 3.
6) Reload http://localhost:8080/scopes/window-scope-A.jsf in second browser.
7) Observe counter value in second browser, it will be 3 instead of 0 as expected.