[
https://jira.jboss.org/jira/browse/RF-3878?page=com.atlassian.jira.plugin...
]
Ian Springer commented on RF-3878:
----------------------------------
Hi,
We noticed that the heap usage for RHQ/JON shot up by like 400MB after 11 users logged
into the (JSF/RichFaces/Seam-based) GUI. I took a heap dump and saw that most of this
memory was being consumed by hefty org.ajax4jsf.util.LRUMaps inside
org.ajax4jsf.application.AjaxStateHolders inside Tomcat Sessions. Googling brought me to
this JIRA issue. I tried the workaround described in the forum post associated with this
issue (setting the com.sun.faces.numberOfViewsInSession and
com.sun.faces.numberOfLogicalViews web.xml context params to 1), but, based on our tests,
that did not lower the heap usage at all. JON is using RF 3.3.0.GA, which is the version
of RF this issue was reportedly fixed in. What was the fix exactly? Was it related to the
getNumberOfViews() method Brian Kates mentions above? Is there some other RF web.xml param
we need to set to enable the fix?
Thanks,
Ian
Session memory leak
-------------------
Key: RF-3878
URL:
https://jira.jboss.org/jira/browse/RF-3878
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 3.2.0.SR1
Reporter: Dmitri Voronov
Assignee: Nick Belaevski
Fix For: 3.3.0
AjaxStateHolder saves all views in the session. But the same view can occur several times
in this "cache"; the views from this "cache" are not reused and just
fill the session. If an application has many large views and deals with many concurrent
sessions, the heap can easily grow up to Gigabytes(!)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira