Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.8.2-EE-GA_P01
-
Fix Version/s: 1.8.3, 1.8.2-EE-GA_P02
-
Component/s: None
-
Labels:None
-
Environment:Linux dingbat 2.6.18-128.el5 #1 SMP Wed Jan 21 08:45:05 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
Firefox 3.6
IE 8
-
Workaround Exists:Yes
-
Workaround Description:
Description
Create two separate Glassfish domains, and deploy an ICEfaces application into each of them. The two domains are completely separate, with their own ports. They are standalone domains (they are not in a cluster).
Individually, a browser on a client can use each on their own without error.
However, we have found the following scenario.
1) Connect to the application in domain A. Call this Browser A.
2) On the same client machine, open another Tab/Window/Session in the browser and connect to the application in domain B. Call this Browser B.
3) Once Browser B has connected, Browser A displays the message we display when an Ice.onSessionExpired event is received. So Browser A's session has expired.
4) One the OK button is clicked in Browser A in the dialog with the session expiry message, Browser B's session is expired and displays the message.
Surely the applications running on different domains on the same host machine should be available to the same client without this sort of impact?
Individually, a browser on a client can use each on their own without error.
However, we have found the following scenario.
1) Connect to the application in domain A. Call this Browser A.
2) On the same client machine, open another Tab/Window/Session in the browser and connect to the application in domain B. Call this Browser B.
3) Once Browser B has connected, Browser A displays the message we display when an Ice.onSessionExpired event is received. So Browser A's session has expired.
4) One the OK button is clicked in Browser A in the dialog with the session expiry message, Browser B's session is expired and displays the message.
Surely the applications running on different domains on the same host machine should be available to the same client without this sort of impact?
Activity
Ed Hillmann
created issue -
Ed Hillmann
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | icefacesBugReport-1.0-SNAPSHOT.war [ 12456 ] | |
Attachment | icefacesBugReport_src.zip [ 12457 ] |
Ken Fyten
made changes -
Salesforce Case | [] | |
Fix Version/s | 1.8.2-EE-GA_P02 [ 10226 ] | |
Fix Version/s | 1.8.3 [ 10211 ] | |
Assignee | Deryk Sinotte [ deryk.sinotte ] |
Deryk Sinotte
made changes -
Salesforce Case | [5007000000D2wCm] |
Deryk Sinotte
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Won't Fix [ 2 ] |
Deryk Sinotte
made changes -
Workaround Description |
Configure separate domains. Instead of this: myhost.org:8080/context1 myhost.org:8085/context2 do this: webapp1.myhost.org/ webapp2.myhost.org/ |
|
Workaround Exists | [Yes] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
This is a sample application with which we can recreate this issue. I've included the WAR file, as well as the source used to construct it.
One note: if each domain uses a different context root for the deployed application, then we don't get the error. However, this is not a feasible long-term solution for us.