You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by ohfaces <ne...@yahoo.com> on 2007/05/31 21:08:26 UTC

Memory leak issues with MyFaces 1.1.3?

Hi,

I have a customer-facing application that is running on IBM JVM 1.5 and
Oracle App Server 10.1.3. The app uses MyFaces 1.1.3 release and has been in
production since the last 3-4 months.
The load tests prior to production went fine with the samples provided by
the client, but now in production we are observing memory leak scenarios
possibly due to the MyFaces JSPStateManagerImpl / it's handling of the
internal SerializedViewCollection objects or it's interaction with the
Apache Commons library.
What we observed on heapdumps is that the MyFaces JSPStateManagerImpl takes
a huge amount of heap on running the app for 3-4 days and eventually takes a
lot of the memory on the heap making it less available for the rest of the
app.

Here's the results from one of the heapdump attached as an image to this
mail.



Also, on looking at the instance counts of the MyFaces SerializedKey we see
that it keeps on increasing with time despite turning Serialization off and
reducing the number of cached views in session to 4.

Is it possible that these settings do not have any effect on Myfaces 1.1.3
and has such a memory leak been reported earlier?

We plan on updating to MyFaces 1.1.5 - to see if this fixes the issue with
the JSPStateManagerImpl .... but it's still up in the air.

Thanks in advance! http://www.nabble.com/file/p10900138/heapdump.gif 
-- 
View this message in context: http://www.nabble.com/Memory-leak-issues-with-MyFaces-1.1.3--tf3848348.html#a10900138
Sent from the MyFaces - Users mailing list archive at Nabble.com.