Adrian Sobotta wrote:
...
My problem however is that it slowly it eats up more and more memory. So
after 500 pdf's or so its used more then the 500MB that I'm allowing the JVM
to use and it dies with the following error:
...
Exception in thread "main" java.lang.OutOfMemoryError
There are several possiblities:
- FOP's image cache is filled. If you don't reuse images across documents,
call FOPImageFactory.resetCache() after every call to render(). If you
reuse image heavily, call it after every tenth rendering or if free
memory runs low or whatever, get some data and do the fine tuning yourself.
- You are creating memory leaks: hold references to driver objects, open
streams whatever. Get a memory profiler in order to track this down and
ensure you don't hold onto references indefinitely.
- Memory leaks in the JVM. Well, the only work around this is to use another
JVM or complain to the vendor.
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
