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"
When the window ID cannot be matched against any of the scope maps (active or disposed) then most probably a postback was received after the server or application was restarted. Create a freshly new ScopeMap to be used by the rest of the JSF lifecycle and by next page load (if issued during a reload).