Cédric Augustin wrote:
Do I have to manualy reset the fop image cache or does fop reset itself ?
FOP does not reset the image cache. You'll have to call the
FopImageFactory.resetCache() method by yourself. If your image
pool is stable and is small enough that all the images can be kept
in the image cache, you don't need to fiddle with the cache.
Slow changes in the image pool are usually accommodated by weekly
or biweekly server restarts or server downtime for maintenance.
If i create a dedicated method in my servlet to reset the cache should I
take care about anything special ?
Probably not.
My cheef don't think it's the image cache the problem, do you have any
suggestion to investigate ?
There are no known memory leaks in FOP 0.20.5 except for the image
cache and a string buffer used in the PDF renderer, which usually
wont grow beyond a few Kilobytes. Once the Driver object is reclaimed,
all other memory allocated during rendering will be freed to. Be sure
to avoid keeping references to Driver objects you no longer need.
You can try one of the memory debuggers which can be attached to a
running program and which will tell you which objects hang around
in memory. If no redering is in progress and you still see FOP objects
other than FopImage, element mappings/makers and FOP configuration data,
something went wrong. Keep an eye on Java stream objects, specifically
related to configuration data and user font loading.
As a cheap but still efficient measure, you can try DrMem:
http://java-source.net/open-source/profilers/drmem
J.Pietschmann
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
