Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Invalid
-
Affects Version/s: EE-3.3.0.GA_P03
-
Fix Version/s: EE-3.3.0.GA_P04
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P2
-
Support Case References:Support Case #13725 - https://icesoft.my.salesforce.com/5007000001Zn5fh
Description
This is a similar issues as described in ICE-6931. The instances of the DynamicResourceDispatcher are not being cleaned up when the users session has expired. The instances of this class are created when the ice:outputResource is rendered on the page.
Activity
Arran Mccullough
created issue -
Arran Mccullough
made changes -
Field | Original Value | New Value |
---|---|---|
Attachment | visualvm-after-session-exp.jpg [ 22115 ] | |
Attachment | visualvm-before-session-exp.jpg [ 22116 ] |
Ken Fyten
made changes -
Assignee | Mircea Toma [ mircea.toma ] | |
Fix Version/s | EE-3.3.0.GA_P04 [ 12270 ] | |
Assignee Priority | P2 [ 10011 ] |
Mircea Toma
made changes -
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Invalid [ 6 ] |
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Attached screen shots of the VidualVM monitoring of the classes. There is no change before the session has expired compared to when the users session had expired.
I was reproducing this with the Showcase demo from the EE 3.3.0 P03 release on Tomcat 8. I made the following changes in the demo web.xml:
Changed:
<session-config>
<session-timeout>1</session-timeout>
</session-config>
Added:
<context-param>
<param-name>org.icefaces.strictSessionTimeout</param-name>
<param-value>true</param-value>
</context-param>
This was to facilitate the timely expiry of the session.