]
Sent: Tuesday, June 15, 2010 12:06 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: AW: AW: AW: GC overhead limit exceeded on a 64-bit jvm
On Mon, 14 Jun 2010 16:47:11 +0300, Georg Datterl
georg.datt...@geneon.de wrote:
The ant task has to start a java VM, too. You just have to find out
GmbH: www.willmycc.de
-Ursprüngliche Nachricht-
Von: Mario Madunic [mailto:mario_madu...@newflyer.com]
Gesendet: Montag, 14. Juni 2010 15:13
An: fop-users@xmlgraphics.apache.org
Betreff: RE: AW: AW: GC overhead limit exceeded on a 64-bit jvm
I've been following these GC
-users@xmlgraphics.apache.org
Subject: AW: AW: AW: GC overhead limit exceeded on a 64-bit jvm
Hi Mario,
It's a VM option. I don't think the variable is used already, so either you
implement it or hardcode the vm switch into your start script.
Regards,
Georg Datterl
-- Kontakt --
Georg
: www.willmycc.de
-Ursprüngliche Nachricht-
Von: Mario Madunic [mailto:mario_madu...@newflyer.com]
Gesendet: Montag, 14. Juni 2010 15:42
An: fop-users@xmlgraphics.apache.org
Betreff: RE: AW: AW: GC overhead limit exceeded on a 64-bit jvm
So I'm guessing this option is unavailable to the FOP
On Mon, 14 Jun 2010 16:47:11 +0300, Georg Datterl
georg.datt...@geneon.de wrote:
The ant task has to start a java VM, too. You just have to find out,
where the VM is started and set the switch there.
In case you don't want to dig into ant or fop startup scripts, a quick
and dirty