Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-1.8.2.GA_P04
-
Fix Version/s: EE-1.8.2.GA_P05
-
Component/s: Framework
-
Labels:None
-
Environment:ICEfaces, Tomcat 6.0.18
-
Assignee Priority:P2
-
Salesforce Case Reference:
Description
The purpose of this JIRA is to investigate a potential memory leak in our code and apply a fix proposed by one of our customers if applicable.
Customer's description:
In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\).
The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards.
Customer's description:
In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\).
The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Reporter | Migration [ remote ] | Evgheni Sadovoi [ evgheni.sadovoi ] |
| Attachment | Proposed changes.docx [ 14900 ] |
| Attachment | Proposed changes.docx [ 14901 ] |
| Assignee | Deryk Sinotte [ deryk.sinotte ] | |
| Fix Version/s | EE-1.8.2.GA_P05 [ 10331 ] | |
| Assignee Priority | P2 [ 10011 ] |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Security | Private [ 10001 ] |
| Description |
The purpose of this JIRA is to investigate a potential memory leak in our code and apply a fix proposed by one of our customers if applicable. Customer's description: In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\). The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards. |
The purpose of this JIRA is to investigate a potential memory leak in our code and apply a fix proposed by one of our customers if applicable.
Customer's description: In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\). The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards. Environment: • Liferay 5.2.3 + Tomcat 6.018 • ICEfaces EE-1.8.2.GA_P04 • ICEfaces is installed as a shared library • Cookies are configured to be all stored under the root context (Tomcat server.xml: <Connector emptySessionPath="true"… />) Steps to reproduce: 1) Install ICEfaces as a shared library in Tomcat 2) Deploy two separate ICEfaces app .war files to Liferay 3) Create a new portal page and add 1 portlet from each app to the page (target page) 4) Log in to the portal 5) Navigate to the target page 6) Log out from the portal (invalidate portal session) |
| Description |
The purpose of this JIRA is to investigate a potential memory leak in our code and apply a fix proposed by one of our customers if applicable.
Customer's description: In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\). The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards. Environment: • Liferay 5.2.3 + Tomcat 6.018 • ICEfaces EE-1.8.2.GA_P04 • ICEfaces is installed as a shared library • Cookies are configured to be all stored under the root context (Tomcat server.xml: <Connector emptySessionPath="true"… />) Steps to reproduce: 1) Install ICEfaces as a shared library in Tomcat 2) Deploy two separate ICEfaces app .war files to Liferay 3) Create a new portal page and add 1 portlet from each app to the page (target page) 4) Log in to the portal 5) Navigate to the target page 6) Log out from the portal (invalidate portal session) |
The purpose of this JIRA is to investigate a potential memory leak in our code and apply a fix proposed by one of our customers if applicable.
Customer's description: In our application all the contexts used by the same browser in the same application have the same sessionId (cookie JSESSIONID con path=\). The map inside com.icesoft.faces.webapp.http.servlet.SessionDispatcher$Monitor uses the sessionId as the key and the value contains a map of contexts related to that sessionId, the problem is that, when the first context is released, the element is removed from the first map and no other contexts with the same sessionId can be released afterwards. |
| Salesforce Case Reference | 5007000000OC4c2AAD |
| Status | Resolved [ 5 ] | Closed [ 6 ] |