RamanaJV wrote:
> I'm trying to fix the memory snag in the AWT viewer. I experimented
> with other formats too and found that the memory obstacle also exist (not
> much as AWT viewer, but it is there) at the Area Tree construction too.
> Could an experienced FO developer, help me where actua
HI group,
I'm trying to fix the memory snag in the AWT viewer. I experimented
with other formats too and found that the memory obstacle also exist (not
much as AWT viewer, but it is there) at the Area Tree construction too.
Could an experienced FO developer, help me where actually the memo
RamanaJV wrote:
> I have narrowed in on the problem somewhat. Followed Hansuli
> Anderegg and found that the problem is with AWTRenderer itself, with PDF and
> TXT, no OutOfMemory.
Hmm, probably loading swing classes finally exhausts available memory.
--
Oleg Tkachenko
Multiconn Internati
> Now, I request the group to tell me whether there are any PDF
> viewers, that I can use in my JavaApplication to show the thus generated
> output.
There is a PDF bean on the Adobe web site that I used successfully some
time
ago. I think it supports PDF features including PDF 1.1.
Hope this he
show the thus generated
output.
Please, help me
Ramana.
-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 8:53 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException
I have had some similar problem with one document : Some
I have had some similar problem with one document : Some hyphenated text in
a cell that was on two rows (row span) : FOP warned me about some "I cannot
hyphenate!". I have not seen this with small documents (bellow 500 pages)
but with large ones FOP went on an infinite loop. I did exactly like
I have generated the XSL:FO into a file. I have used the FOP -d option
and pasted the debug messages thus got in the attached file "temp". I can
even send the FO file individually to test the load, since the mail to the
mailing test bounces with that attachment.
After these error messages, f
To attack the problem:
o split the job into 2 steps:
- XSL transformation writes XSL:FO to a file
- FOP formats the file
o use another renderer: text e.g.
o vary the input
- reduce the volume: when does it blow up?
- eliminate distinct elements
You will pretty s
Lou is right.
could you tell us what FOP outputs when you use the debug mode ? (-d option
in command line).
Cyril
At 10:53 25/07/2002 -0400, you wrote:
>Ramana:
>Is it dumping out FOP error messages even though the report seems to be
>working? I think these errors can be related to overflows
: Thursday, July 25, 2002 8:23 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException
Ramana:
Is it dumping out FOP error messages even though the report seems to be
working? I think these errors can be related to overflows within your
context areas which I have seen posted as causing increased
:42:32
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: RE: OutofMemoryException
Cyril,
I'm sure that I don't have any forward references and page
footers.
What I have in the page sequence is a static text , some blocks followed by
a table. The JDK i
rom: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 7:29 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException
Ramana,
I have a 256 Mo Ram machine that uses JVM -Xms512m -Xmx512m and it runs
fine.
I admit that JVM memory settings gives some weird results sometimes.
#x27;m bugged with
>this OutofMemoryException. My system has 192Mb RAM. The FO document is
>made of tables. There will be two tables per page. There are no forward
>references.
>
>Ramana.
-
To unsubscribe, e-mail: [E
Cyril,
As far your suggestion, I have made the FO to be a small page
sequences (could be around 20 pages per sequence). But, it I'm bugged with
this OutofMemoryException. My system has 192Mb RAM. The FO document is
made of tables. There will be two tables per page. There are no fo
Cyril,
As far your suggestion, I have made the FO to be a small page
sequences (could be around 20 pages per sequence). But, it I'm bugged with
this OutofMemoryException. My system has 192Mb RAM. The FO document is
made of tables. There will be two tables per page. There are no fo
Thanx for the response cyril.
I'll try this. How is your new place?
Ramana.
-Original Message-
From: Cyril Rognon [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 25, 2002 5:58 PM
To: [EMAIL PROTECTED]
Subject: RE: OutofMemoryException
Ramana,
I guess you can find in the
;Sent: Thursday, July 25, 2002 4:19 PM
>To: [EMAIL PROTECTED]
>Subject: Re: OutofMemoryException
>
>
>Hi,
>
>it IS capable of rendering large documents. Out of Memory exception ist just
>caused by standard JVM Memory assignment of 64M.
>Just enlarge the memory for
]
Subject: Re: OutofMemoryException
Hi,
it IS capable of rendering large documents. Out of Memory exception ist just
caused by standard JVM Memory assignment of 64M.
Just enlarge the memory for the JVM with parameter -Xmx256m (256m for
256Megs).
Jochen
- Original Message -
From
ROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 25, 2002 12:14 PM
Subject: OutofMemoryException
> Dear group,
> I have a big fo file, could be around 100 pages. But the driver
> gives me a outofmemoryexception when I give this file to the renderer. I
use
> AWTRenderer fo
Dear group,
I have a big fo file, could be around 100 pages. But the driver
gives me a outofmemoryexception when I give this file to the renderer. I use
AWTRenderer for printing the document. Can't FOP handle big FO documents. Is
there a workaround to get around this memory pr
20 matches
Mail list logo
