xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46319] OutOfMemoryError after generating several thousand pdfs
Date Tue, 02 Dec 2008 09:19:30 GMT

--- Comment #6 from Jeremias Maerki <jeremias@apache.org>  2008-12-02 01:19:29 PST ---
(In reply to comment #4)
> The webapplication runs on 64 bit linux. The 3GB memory are needed to run about
> 300 parallel sessions with about 1000 request per minute, where as 10% are pdf
> requests and the rest http.
> We already limit the maximum number of parallel fop requests by using a pool of
> 3 pfdTransformer objects.
> We blame fop 0.95 to be problem cause because the application runs without
> problems when turning of the pdf requests or when using old fop 0.20.5 for pdf
> generation. 
> I just started some investigations with profiler - it looks like a few kb
> (~2kB) of memory get lost per pdf. I hope the attached screenshot helps to find
> the potential problem cause.

I'm afraid, I can't read anything out of this screenshot. When we fixed the
property cache problems, http://www.alphaworks.ibm.com/tech/heapanalyzer was
very handy to analyze head dumps and find the leaks.

Anyway, there's still that strange OutOfMemoryError which I've never seen
myself before. Maybe you're seeing two different problems here. I would still
check what happens if you lower the max heap setting (if the OutOfMemoryError
changes, it's an indicator). And if the OutOfMemoryError persists it can make
sense to see if the problem goes away if you use FOP Trunk instead. You can
also try to backport the property cache fix to the 0.95 branch but that could
be a bit of work.

Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

View raw message