than 4,500 lines I get the out-of-memory error.
Currently, the entire invoice is one page-sequence. Your approach
appears to solve that problem and will keep the paging in tact. My
problem is finding a way to create multiple page-seq inside a single
table without ruining the spacing.
I am working
uary 22, 2009 4:11 AM
> To: fop-users@xmlgraphics.apache.org
> Subject: Re: Out of Memory Error from Java
>
> Steffanina, Jeff wrote:
>
>> I have:
>> FOP 0.95
>> Linux
>> Java 1.5
>> My Java starts with memory set as: -
, January 22, 2009 4:11 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Out of Memory Error from Java
Steffanina, Jeff wrote:
> I have:
> FOP 0.95
> Linux
> Java 1.5
> My Java starts with memory set as: -Xmx192m
>
> I can print an unlimited
where each invoice contains 100 lines of details.
Therefore, print a total of 200,000 lines of detail.
However, I receive an "Out of Memory" error from Java when I attempt to
print a single invoice that contains more than 4,500 lines of detail.
Have you read: http://xmlgraphics.
100 lines of details.
Therefore, print a total of 200,000 lines of detail.
However, I receive an "Out of Memory" error from Java when I attempt to
print a single invoice that contains more than 4,500 lines of detail.
Other than continuing to increase the amount of memory at startup
max. Well, even 40-50 pages should work nicely, and with 2GB of heap,
> I guess this could even be a lot more...
>
>
> Cheers
>
> Andreas
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.
On 12 Dec 2008, at 15:28, Griffin,Sean wrote:
Hi Sean, Vsyamala,
I was assuming you were embedding FOP into your application and
calling directly through Java. Since it appears you're launching
from the command-line, it's up to the FOP command-line program on
how it streams the output. S
to finding the source of your problem:
http://xmlgraphics.apache.org/fop/0.94/running.html#memory.
Sean
-Original Message-
From: vsyamala [mailto:vsyam...@gmail.com]
Sent: Friday, December 12, 2008 8:12 AM
To: fop-users@xmlgraphics.apache.org
Subject: RE: Out of Memory error
Hi Sean,
Tha
fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.
> java:526)
> at
> org.apache.fop.render.AbstractRenderer.renderBlock(AbstractRenderer.j
> ava:573)
> at
> org.apache.fop.render.pdf.PDFRenderer.renderBlock(PDFRenderer.java:13
> 29)
>
.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.
java:526)
Thanks,
Vsyamala
--
View this message in context:
http://www.nabble.com/Out-of-Memory-error-tp20962360p20962360.html
Sent from the FOP - Users mailing list archive at Nabble.com.
-
nderer.
java:526)
Thanks,
Vsyamala
--
View this message in context:
http://www.nabble.com/Out-of-Memory-error-tp20962360p20962360.html
Sent from the FOP - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
CTED]
Gesendet: Dienstag, 9. September 2008 13:16
An: fop-users@xmlgraphics.apache.org
Betreff: Re: AW: Font autodetection yields Out-of-Memory error
Please note that an OutOfMemoryError can occur anywhere. A stack trace
in such a case is not an reliable indicator for a problem.
I don't think there&
sense to catch EOF here as well?
>
> Greetings, Ingo
>
> -Ursprüngliche Nachricht-
> Von: Adrian Cumiskey [mailto:[EMAIL PROTECTED]
> Gesendet: Montag, 8. September 2008 18:15
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: Font autodetection yields Out-of
endet: Montag, 8. September 2008 18:15
An: fop-users@xmlgraphics.apache.org
Betreff: Re: Font autodetection yields Out-of-Memory error
Hi Ingo,
Looking at the stack trace it doesn't look to be a problem with font
autodetection, more to do with
a parsing problem on one of your PFM files. I
e.org
Betreff: Re: Font autodetection yields Out-of-Memory error
Hi Ingo,
Looking at the stack trace it doesn't look to be a problem with font
autodetection, more to do with
a parsing problem on one of your PFM files. I'm guessing it must be an
erroneous one as I wasn't
able to r
Hi Ingo,
Looking at the stack trace it doesn't look to be a problem with font autodetection, more to do with
a parsing problem on one of your PFM files. I'm guessing it must be an erroneous one as I wasn't
able to reproduce the problem with the PFM font file that I tried.
Could you try isola
Hallo,
In font autodetection seems to be a bug, introduced sometime in June/July. I
hoped that this has been fixed in 0.95 or current trunk, but it has not. See
stacktrace for current trunk below.
Regards, Ingo
Stacktrace: java.lang.OutOfMemoryError: Java heap space
at java.lang
x27;t have images (they were data catalogs for a data warehouse).
Jay Bryant
Bryant Communication Services
- Original Message -
From: [EMAIL PROTECTED]
To: fop-users@xmlgraphics.apache.org
Sent: Tuesday, February 06, 2007 4:54 PM
Subject: Out Of Memory Error
Hello All,
Check the FAQ:
http://xmlgraphics.apache.org/fop/0.93/running.html#memory
Regards,
Roland
[EMAIL PROTECTED] wrote:
Hello All,
I am trying to convert a huge XML document(approx about 110 pages
long, 777KB) into a pdf document using an FO transformation. But it
gives me the following error
Hello All,
I am trying to convert a huge XML document(approx about 110 pages long,
777KB) into a pdf document using an FO transformation. But it gives me
the following error.
Exception in thread "main" java.lang.OutOfMemoryError
Can anybody guide me as to what is going wrong? Is there a limit on
On 30.08.2006 17:30:09 Naveen Bandhu wrote:
>
> Currently we are using fop version 0.20.5, and get Out of memory error. I
> have seen the fix in trunk but we cant use the trunk because of the changes
> we have to do for XSL files to make our them compatiable to trunk version.
That
Currently we are using fop version 0.20.5, and get Out of memory error. I have seen the fix in trunk but we cant use the trunk because of the changes we have to do for XSL files to make our them compatiable to trunk version. As per the fix in trunk, PageSequence.java has new method public void
Please respond to
fop-users@xmlgraphics.apache.org
To
fop-users@xmlgraphics.apache.org
cc
Subject
Re: out of memory error
On Aug 9, 2006, at 14:34, Luis Ferro wrote:
Hi,
> I'm using the latest fop version from svn as of yesterday...
>
> In the attachment i send the
message in context:
http://www.nabble.com/out-of-memory-error-tf2044079.html#a5738048
Sent from the FOP - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Not sure that playing with the page-masters will really help. I don't
think they have an influence here.
I've just committed a helper XSLT [1] which can split Luis' FO file at
page-sequence boundaries. It reveals that one of the page-sequences
alone makes up 18MB out of the 23MB of the full FO fil
On Aug 9, 2006, at 19:27, Luis Ferro wrote:
Hi,
It has LOADS of page sequences... it's a book with 2500 pages where
from 3 or
4 pages, the "template" changes from one column page to 2 column
page...
Is there a better way of doing this "swap" of columns?
Not that I'm aware of... (you're u
... (my
machine has a top of 1.5Gb adressable to java...)...
Will try now to simplefy everything as best as i can...
How can i test if there is memory leaks somewhere (i'm a programmer but i'm
very very green in java)?
Cheers...
LF
--
View this message in context:
http://www.nabble.com
On Aug 9, 2006, at 14:34, Luis Ferro wrote:
Hi,
I'm using the latest fop version from svn as of yesterday...
In the attachment i send the files i use to create a PDF with the
index and
one chapter of the book. The index references are all turned off
but it
still gets out of heap...
When
thru tomcat it was giving problems, but that is another issue)
Cheers...
LF
--
View this message in context:
http://www.nabble.com/out-of-memory-error-tf2044079.html#a5728922
Sent from the FOP - Users forum at Nabble.com.
-
eutico/extranet/makebook/output/makebook_done_wi
th_images_1.fo:3978:33 No meaningful layout in block after many attempts.
Infin
ite loop is assumed. Processing halted.
Hope this "sheeds some light" on the problems...
LF
--
View this message in context:
http://www.nabble.com/out-of-me
vn_20060807.zip
memory_problem_thrunk_svn_20060807.zip
--
View this message in context:
http://www.nabble.com/out-of-memory-error-tf2044079.html#a5724811
Sent from the FOP - Users forum at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additio
8.2006 09:06:34 Madala, Leena \(GE Healthcare, consultant\) wrote:
> Hello team,
>
> I'm facing similar issue. I'm getting out of memory error, when trying
> to generate a report.
> I have checked FAQ and tried all the options provided there...
>
> I tried increasing
Hello team,
I’m facing similar issue. I’m
getting out of memory error, when trying to generate a report.
I have checked FAQ and tried all the
options provided there…
I tried increasing Java virtual memory to
1024M and also removed page citation in the report generated. I also
Yes. I'm pretty sure you won't need to clear the image cache anymore.
BTW, I'd appreciate feedback concerning memory consumption if anyone
runs the latest FOP Trunk with many images. It would be good to know if
I really hit the right nail.
On 26.07.2006 18:27:39 Dominic Brügger wrote:
> Is the pro
Is the problem with the image cache that I described a few weeks ago now solved too?On 26.07.2006, at 15:07, Jeremias Maerki wrote:Change was last week.On 26.07.2006 14:38:39 Rick Roen wrote: Jeremias - I am running from trunk code from about a month ago. Have youdone some memory adjustments since
Change was last week.
On 26.07.2006 14:38:39 Rick Roen wrote:
> Jeremias - I am running from trunk code from about a month ago. Have you
> done some memory adjustments since then?
Jeremias Maerki
-
To unsubscribe, e-mail: [EMA
Rick Roen wrote:
Jeremias - I am running from trunk code from about a month ago. Have you
done some memory adjustments since then? I remember I used to have extra
large resulting PDF files when I had an image that did not have a color
table (or something ?), but the trunk code brought a 225KB
the trunk code brought a 225KB file back down to
25KB.
Rick
-Original Message-
From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 26, 2006 2:00 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: out of memory error
20 to 25 pages does not really count as "ext
EMAIL PROTECTED]
Verzonden: woensdag 26 juli 2006 9:03
Aan: fop-users@xmlgraphics.apache.org; [EMAIL PROTECTED]
Onderwerp: RE: out of memory error
> -Original Message-
> From: Rick Roen [mailto:[EMAIL PROTECTED]
>
> Update...
>
> I was googling in the wrong place. When I lo
> -Original Message-
> From: Rick Roen [mailto:[EMAIL PROTECTED]
>
> Update...
>
> I was googling in the wrong place. When I looked in Java I
> found the switch "-XX:+AggessiveHeap" which fixed the problem.
>
> Is this the best switch to use, or is there something better?
Hi Rick,
Yo
t;
>
>
> Rick
>
>
>
> _
>
> From: Rick Roen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, July 25, 2006 4:12 PM
> To: fop-users@xmlgraphics.apache.org
> Subject: out of memory error
>
>
>
> I'm running FOP from the current build of
, 2006 4:12
PM
To:
fop-users@xmlgraphics.apache.org
Subject: out of memory error
I’m running FOP from the current build of about a
month ago on XP Pro SP2 1.5GB RAM
I have a command line routine that runs sales documents
(packing list, invoice etc.) from xml .-> xslt (using Saxon 8
)-&
I’m running FOP from the current build of about a
month ago on XP Pro SP2 1.5GB RAM
I have a command line routine that runs sales documents
(packing list, invoice etc.) from xml .-> xslt (using Saxon 8 )->pdf.
This works with no problem except when I have an extra large
document (m
43 matches
Mail list logo
