Hi Georg, I second what Andrey says. I was getting out of memory issues when ever I tried to iterate over 5000 elements within a single page sequence. I solved this by splitting the big parts of the document into separate page sequences as FOP releases memory after each page sequence. Good luck
>>> Georg Datterl <georg.datt...@geneon.de> 09/06/2010 16:35 >>> Hi Andrey, Other than that you can: · Decrease the number of pages in one page-sequence (means changing the fo file). · Change the gc-paramter of your VM. Continual GC keeps the system from GCing until timeout ( parameter when starting fop) · If you have lots of images, all of them used once, you can turn off image caching. ( parameter when starting fop) The overflow messages you see are not memory overflows but print area overflows. Basically you have a block which contains more text than fits into the block. The text is printed beyond the border of the block and a warning is generated. If the space, where the text is printed into is empty otherwise, there’s no harm done and everything is fine. Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de Willmy PrintMedia GmbH: www.willmy.de Willmy Consult & Content GmbH: www.willmycc.de Von:Eric Douglas [mailto:edoug...@blockhouse.com] Gesendet: Mittwoch, 9. Juni 2010 17:18 An: fop-users@xmlgraphics.apache.org Betreff: RE: Java Heap You can't generate big files, or you need more memory. More memory could be referring to either your physical system memory or your allocated Java memory. This should have norhing to do with your line overflows. Make text smaller or blocks bigger. In my usage, I just put a condition that would tell the user don't do that if they try to print a report over like 1000 pages. I'm not sure where the memory cutoff would be, but they should normally never need giant reports. A report that big typically means they need to enter more criteria to limit results. I'm sure there's a workaround to print giant reports if there is a need. Maybe you could try creating multiple PDFs and combining? Maybe there's a fix in the Trunk? I haven't bothered to figure out how because it's easier to say don't do that. To figure out why you're overflowing, someone would most likely need to see your actual XML/XSL/FO code. I have mine dynamically setting the font size and block size to make sure it fits. From:Andrey Skrypnik [mailto:askryp...@meritservus.com] Sent: Wednesday, June 09, 2010 10:57 AM To: fop-users@xmlgraphics.apache.org Subject: Java Heap Hi guys, I’m using FOP 0.95 i when i try to generate a big file i received: SEVERE: Servlet.service() for servlet meritservus threw exception java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOfRange(Arrays.java:3209) at java.lang.String.<init>(String.java:215) at java.lang.StringBuffer.toString(StringBuffer.java:585) at java.io.StringWriter.toString(StringWriter.java:193) but before i have a huge amount of rows: WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 3226mpt. (fo:block, "LVBND_2624500") 17:16:06.688 WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 3226mpt. (fo:block, "LVBND_2624500") 17:16:06.688 WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 3226mpt. (fo:block, "LVBND_2624500") 17:16:06.813 WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 12906mpt. (fo:block, "COMMUNICATIONS") 17:16:09.985 WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 12906mpt. (fo:block, "COMMUNICATIONS") 17:16:10.423 WARN [http-8080-3] org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm:388 - Line 1 of a paragraph overflows the available area by 14890mpt. (fo:block, "SAMPLE_PORT_USD") Please, help me, how I can fix it!!!!!!!!! Thanks a lot! __________ Information from ESET NOD32 Antivirus, version of virus signature database 5184 (20100609) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com This message and any attachments are intended for the persons named as addressees only and may contain confidential information. In addition they may be protected by copyright. If you receive it in error, notify us, delete it and do not make use of or copy it. You must not copy, disseminate or otherwise distribute or publish this message, except for the purposes for which this message is intended, without our consent. Please note that this e-mail has been created in the knowledge that Internet e-mail is not a 100% secure communications medium. We advise that you understand and accept this lack of security when e-mailing us. For company information, guidance and how to file documents online, please see our website www.companieshouse.gov.uk. This message has been scanned for viruses by Hosted Security, a service from Websense.
