AW: AW: Java Heap

2010-06-10 Thread Georg Datterl 
Hi Lea,

See the first bullet in my list. But that might not be possible if the fo file 
is provided by external sources.

I just remembered reading about an experimental feature which made fop release 
memory while still in the same page-sequence. You can search the fop-dev 
archive for a message from Ben Wuest, posted around 3.6.2009, 22:48, subject: 
Apache FOP 0.95 Patch.
This patch requires a modification of FOP, but is based on FOP 0.95, not trunk. 
Actually, I have no idea if the patch made it into trunk.

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<http://www.geneon.de>

Weitere Mitglieder der Willmy MediaGroup:

IRS Integrated Realization Services GmbH:
www.irs-nbg.de<http://www.irs-nbg.de>
Willmy PrintMedia GmbH:
www.willmy.de<http://www.willmy.de>
Willmy Consult & Content GmbH: 
www.willmycc.de<http://www.willmycc.de>

Von: Lea Farmer [mailto:lfar...@companieshouse.gov.uk]
Gesendet: Donnerstag, 10. Juni 2010 11:18
An: Georg Datterl; fop-users@xmlgraphics.apache.org
Betreff: Re: AW: Java Heap

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  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<http://www.geneon.de>
Weitere Mitglieder der Willmy MediaGroup:
IRS Integrated Realization Services GmbH:
www.irs-nbg.de<http://www.irs-nbg.de>
Willmy PrintMedia GmbH:
www.willmy.de<http://www.willmy.de>
Willmy Consult & Content GmbH: 
www.willmycc.de<http://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.(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

Re: AW: Java Heap

2010-06-10 Thread Lea Farmer 
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  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.(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,

AW: Java Heap

2010-06-09 Thread Georg Datterl 
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.(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