Hi Andre,
this parameter defines how many views are stored in memory - and
therefore enable back-button usage with server-side state saving
enabled. Try to set this option to 0, and then try to use the
back-button with server-side state saving - it won't work.
A symptom: you will have to click
Yes, this helps. The OldGen no longer maxes out, and the memory behavior
is the same as when I've removed the _oldSerializedView collection
completely, so this was a simpler solution.
But I must say this is a peculiar parameter. From what I gather, it
defines an upper limit on the number of times
interesting. Actually it's using a soft reference. What if you substitute
_oldSerializedViews = new ReferenceMap();
by
_oldSerializedViews = new ReferenceMap(AbstractReferenceMap.WEAK,
AbstractReferenceMap.WEAK, true);
?
I'm curious if the behaviour is still the same.
Thomas
On 6/4/07, André
Hi
We are working on a JSF project and recently started stress testing the
system. This stress-testing caused the JVM to run out of memory and
spend most of it time doing Full GC. Analyzing the heap revealed that
most of the memory was being retained by SerializedViewCollection
instances. We also
