DO NOT REPLY [Bug 23342] New: - OutOfMemoryError exception processing large XML files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23342. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23342 OutOfMemoryError exception processing large XML files Summary: OutOfMemoryError exception processing large XML files Product: Fop Version: 0.20.5 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Critical Priority: Other Component: pdf renderer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Problem: I get an OUT OF MEMORY exception (without stack trace), while processing large XML files: Exception in thread main java.lang.OutOfMemoryError I've tried with a 100 node XML file (784 Kb) and it worked. I've tried with a 150 node XML file (1.176 KB) and it crashed at [INFO] [82]. It seems that there's some sort of limit to 1 MB... I've monitored the mem usage on the Task Manager and it was using approximatively 80 MB RAM + 80 MB Virtual Memory (I've only 256 MB ram on the computer I'm testing, but I've tried on a 512 MB ram computer too, with the same results). Versions: OS Windows2000 SP4 (build 2195) FOP 0.20.5 (and the libs distributed with that package) j2sdk 1.4.1.02 This is a piece of the XML file: Plichi Plico IDOrdine=65 Cliente=NRG Campagna=Firenze TargetDesc=Famiglie, Negozi, Uffici IDPallet=5507 Canale=B NrPlico=1 TotPlichi=68 NomeUdR=FIRENZE RECAPITO CAMPO DI MARTE DataInizio=09/07/2003 DataFine=16/07/2003 Zone Zona Cella=1 Nr=1 Sel=s/ Zona Cella=2 Nr=2 Sel=s/ Zona Cella=3 Nr=3 Sel=s/ Zona Cella=4 Nr=4 Sel=s/ Zona Cella=5 Nr=5 Sel=s/ Zona Cella=6 Nr=6 Sel=s/ Zona Cella=7 Nr=7 Sel=s/ Zona Cella=8 Nr=8 Sel=s/ Zona Cella=9 Nr=9 Sel=s/ Zona Cella=10 Nr=10 Sel=s/ Zona Cella=11 Nr=11 Sel=s/ Zona Cella=12 Nr=12 Sel=s/ Zona Cella=13 Nr=13 Sel=s/ Zona Cella=14 Nr=14 Sel=n/ Zona Cella=15 Nr=15 Sel=s/ Zona Cella=16 Nr=16 Sel=s/ Zona Cella=17 Nr=17 Sel=n/ Zona Cella=18 Nr=18 Sel=s/ Zona Cella=19 Nr=19 Sel=s/ Zona Cella=20 Nr=20 Sel=n/ Zona Cella=21 Nr=21 Sel=n/ Zona Cella=22 Nr=22 Sel=s/ Zona Cella=23 Nr=23 Sel=s/ Zona Cella=24 Nr=24 Sel=s/ Zona Cella=25 Nr=25 Sel=s/ Zona Cella=26 Nr=26 Sel=s/ Zona Cella=27 Nr=27 Sel=n/ Zona Cella=28 Nr=28 Sel=s/ Zona Cella=29 Nr=29 Sel=s/ Zona Cella=30 Nr=30 Sel=s/ Zona Cella=31 Nr=31 Sel=s/ Zona Cella=32 Nr=32 Sel=s/ Zona Cella=33 Nr=33 Sel=s/ Zona Cella=34 Nr=34 Sel=s/ Zona Cella=35 Nr=35 Sel=s/ Zona Cella=36 Nr=36 Sel=s/ Zona Cella=37 Nr=37 Sel=s/ Zona Cella=38 Nr=38 Sel=s/ Zona Cella=39 Nr=39 Sel=s/ Zona Cella=40 Nr=40 Sel=s/ Zona Cella=41 Nr=41 Sel=s/ Zona Cella=42 Nr=42 Sel=s/ Zona Cella=43 Nr=43 Sel=s/ Zona Cella=44 Nr=44 Sel=s/ Zona Cella=45 Nr=45 Sel=s/ Zona Cella=46 Nr=46 Sel=s/ Zona Cella=47 Nr=47 Sel=s/ Zona Cella=48 Nr=48 Sel=s/ Zona Cella=49 Nr=49 Sel=s/ Zona Cella=50 Nr=50 Sel=s/ Zona Cella=51 Nr=51 Sel=s/ Zona Cella=52 Nr=52 Sel=s/ Zona Cella=53 Nr=53 Sel=n/ Zona Cella=54 Nr=54 Sel=s/
DO NOT REPLY [Bug 23342] - OutOfMemoryError exception processing large XML files
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23342. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23342 OutOfMemoryError exception processing large XML files [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2003-09-23 08:11 --- This is not actually a bug. The memory is not fixed to 1Mb. Its just that processing XSL-FO is a resource intensive task. Please follow the link for suggestions on how to solve this issue; http://xml.apache.org/fop/running.html#memory You will find the mailing lists helpful for answering any questions you may have. BTW, please can you attach sample files to the bug rather than just pasting their contents in. Thanks
DO NOT REPLY [Bug 23317] - FOP url Rendering issue.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317 FOP url Rendering issue. [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WONTFIX --- Additional Comments From [EMAIL PROTECTED] 2003-09-23 22:18 --- The PDF document is doing the same thing on my side as yours. But, I ran your xml xsl through Xalan--one thing I noticed in the FO output are lots of nonsensical  (A-caret?) letters--I don't see why you need them. There appears to be something wrong with your stylesheet. Also, running the FO output through FOP gave a warning that you have specified your column widths about 25% too wide. (Sum about 500K, specified IPD 417K or so.) This may be the source of your problem--your columns are too narrow, and your results would therefore be undefined. Also, there were complaints about missing images, etc., so that may be an issue. Finally, in a separate, simple document I created two PDF links--one outside a table and one within in a simple file in 0.20.5--works fine!--So I believe the problem is with your XSL FO document. I'm attaching a sample XSL FO document and resultant PDF--you can see that the links work fine. Somehow, perhaps by correcting your XSL FO you should be able to get the links to work like they do in my sample document. But right now, there are too many things messy/wrong with your stylesheet for it to indicate that the problem is with FOP. At any rate, we are making very few changes to our 0.20.x branch, and given that the fo:basic-link mostly work, changes do not appear called for at this time.
DO NOT REPLY [Bug 23317] - FOP url Rendering issue.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23317 FOP url Rendering issue. --- Additional Comments From [EMAIL PROTECTED] 2003-09-23 22:19 --- Created an attachment (id=8323) working examples of fo:basic-link
Re: DO NOT REPLY [Bug 23317] - FOP url Rendering issue.
glenmazza wrote: But, I ran your xml xsl through Xalan--one thing I noticed in the FO output are lots of nonsensical (A-caret?) letters--I don't see why you need them. Looks like *the* typical encoding problem: One (or more) of the posted files was probably UTF-8 encoded but interpreted as ISO-8859-1. Also, running the FO output through FOP gave a warning that you have specified your column widths about 25% too wide. (Sum about 500K, specified IPD 417K or so.) This may be the source of your problem--your columns are too narrow, and your results would therefore be undefined. Ahem, the table will simply overrun the margin. This is well defined. Also, there were complaints about missing images... O well. I thought we added this to the bug reporting instructions, but nobody seems to take them seriously. You can count bug reports whith a complex but still complete file set on the fingers of one hand. J.Pietschmann
Re: (Jay) RE: RE: Batik Extension/FOP problem
Quite possibly. FOP does not appear ready for your needs at this time. Glen --- Jay Chiu [EMAIL PROTECTED] wrote: I have not seen the error [ERROR] findHyphenPoss: problem! in previous FOP versions. Could it be some recent change causing this problem? Thanks. Jay Get your own 800 number Voicemail, fax, email, and a lot more http://www.ureach.com/reg/tag On Sat, 13 Sep 2003, Glen Mazza ([EMAIL PROTECTED]) wrote: Jay, I added in a new Batik extension element mapping in our main trunk code--this should help you. It is not perfect--I noticed a hyphenation warning during running your sample fo document; also I ran one of the samples in the Batik directory (I embedded gears.svg into an FO document)--it *appears* to work, but several issues may appear on our side or Batik's that we will need to fix. Please test it out--wait 6 hours for a nightly snapshot to appear (see our Download link on the main FOP page)--any problems you find, please add to Bugzilla, so we can get them fixed. (You'll find a Bugs link on the main FOP page.) Thanks, Glen --- Jay Chiu [EMAIL PROTECTED] wrote: Attached please find a sample fo file with embedded svg object. You may also take a look at the batik samples, xml-batik/samples/extensions/flow/flowtext.svg __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
Re: DO NOT REPLY [Bug 23317] - FOP url Rendering issue.
Thanks--I should have suspected something simple like that, before questioning his stylesheet on that issue. Glen --- J.Pietschmann [EMAIL PROTECTED] wrote: glenmazza wrote: But, I ran your xml xsl through Xalan--one thing I noticed in the FO output are lots of nonsensical  (A-caret?) letters--I don't see why you need them. Looks like *the* typical encoding problem: One (or more) of the posted files was probably UTF-8 encoded but interpreted as ISO-8859-1. __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com
