Oxygen starts the FOP as an external process, specifying a maximum of 400MB. If the physical memory is less than this value, the OS will swap out processes, and the entire machine will work very slow. For large files I recommend to use the FOP from the command line. Breaking the document into multiple files and including them as external entities from a master file will make no difference. You can try to apply FOP individually over each file. Unfortunately, we are not aware of the FOP memory/cpu performances. Please consult http://xml.apache.org for more information. Sean Wheller wrote:

Hi,

SuSE 8.2, JRE,SE 1.4.2-b28, Oxygen 3.0.1 Alpha

FOP transformations on large files still fail. The FOP message notes java out of memory error. I have set internal FOP memory to 400.

Does the machine mem spec make any difference? Obviously the mor RAM and the better the processor the faster the FOP transform, but should I be able to FOP a large file if I only have 256 MB RAM.

...

free in bash shows

total = 251852 used 220552 free 31300

this is following reboot with KDE running, bash shell open and Oxygen.

If I break the large XML document into smaller (modular) files will this improve memory management?

Sean Wheller

__________________________________ Do you Yahoo!? Exclusive Video Premiere - Britney Spears http://launch.yahoo.com/promos/britneyspears/ _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com http://www.oxygenxml.com/mailman/listinfo/oxygen-user