You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@xmlbeans.apache.org by Dm...@toyota.com.au on 2004/10/26 07:30:56 UTC
memory usage in compile
hello everyone,
we are starting to run into more and more problems getting
OutOfMemoryErrors when compiling schemas. The schemas in question aren't
small, and we're compiling several at once. Obviously we can break them
up into smaller compile batches to avoid this, but that is somewhat
frustrating, and I'm not even sure how that would work when it comes to
the static typing of schema types defined in other schemas.
What are other people doing here? Has anyone else faced OOMs compiling?
And before anyone asks, this is how we're compiling:
[build@toyibusdf1 test-console]$ /opt/bea/jrockit81sp2_141_05/jre/bin/java
-Xms1990M -Xmx1990M -classpath
/home/build/dev/export_tJunction_20040906d/tJunction/thirdparty/lib/wlxbea
n.jar:/home/build/dev/export_tJunction_20040906d/tJunction/thirdparty/lib/
xbean.jar com.bea.xbean.tool.SchemaCompiler -src
/home/build/dev/export_tJunction_20040906d/tmp/test-console/schema -out
/home/build/dev/export_tJunction_20040906d/dist/test-console/test-console-
xbean.jar -dl
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/0.1/H
eaders.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/0.1/T
ypes.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/0.1/V
ehicleInventory.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/commo
n/2003/10/20/Types.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/commo
n/2004/04/01/Types.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/heade
rs/2003/10/20/Headers.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/heade
rs/2004/06/21/Headers.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/vehic
leinventory/2003/10/20/VehicleInventory.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/vehic
leinvoiceadvice/2004/01/21/VehicleInvoiceAdvice.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/vehic
leretailpricing/2004/07/26/VehicleRetailPricing.xsd
/home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/vehic
lespecification/2004/04/01/VehicleSpecification.xsd
so we have plenty of memory available...
ideas? suggestions?
cheers
dim
######################################################################
DISCLAIMER:
This email and any attachment may contain confidential information.
If you are not the intended recipient you are not authorized to copy
or disclose all or any part of it without the prior written consent
of Toyota.
Opinions expressed in this email and any attachment are those of the
sender and not necessarily the opinions of Toyota.
Please scan this email and any attachment for viruses.
Toyota does not accept any responsibility for problems
caused by viruses, whether it is Toyota's fault or not.
######################################################################
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org
Re: memory usage in compile
Posted by David Jencks <dj...@gluecode.com>.
I don't know how relevant it is, but the maven xmlbeans plugin has
facilities for including already-compiled xmlbeans for schemas you
include (or is it import?) without regenerating the beans.
david jencks
On Oct 25, 2004, at 10:30 PM, Dmitri.Colebatch@toyota.com.au wrote:
> hello everyone,
>
> we are starting to run into more and more problems getting
> OutOfMemoryErrors when compiling schemas. The schemas in question
> aren't
> small, and we're compiling several at once. Obviously we can break
> them
> up into smaller compile batches to avoid this, but that is somewhat
> frustrating, and I'm not even sure how that would work when it comes to
> the static typing of schema types defined in other schemas.
>
> What are other people doing here? Has anyone else faced OOMs
> compiling?
> And before anyone asks, this is how we're compiling:
>
> [build@toyibusdf1 test-console]$
> /opt/bea/jrockit81sp2_141_05/jre/bin/java
> -Xms1990M -Xmx1990M -classpath
> /home/build/dev/export_tJunction_20040906d/tJunction/thirdparty/lib/
> wlxbea
> n.jar:/home/build/dev/export_tJunction_20040906d/tJunction/thirdparty/
> lib/
> xbean.jar com.bea.xbean.tool.SchemaCompiler -src
> /home/build/dev/export_tJunction_20040906d/tmp/test-console/schema -out
> /home/build/dev/export_tJunction_20040906d/dist/test-console/test-
> console-
> xbean.jar -dl
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> 0.1/H
> eaders.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> 0.1/T
> ypes.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> 0.1/V
> ehicleInventory.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> commo
> n/2003/10/20/Types.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> commo
> n/2004/04/01/Types.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> heade
> rs/2003/10/20/Headers.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> heade
> rs/2004/06/21/Headers.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> vehic
> leinventory/2003/10/20/VehicleInventory.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> vehic
> leinvoiceadvice/2004/01/21/VehicleInvoiceAdvice.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> vehic
> leretailpricing/2004/07/26/VehicleRetailPricing.xsd
> /home/build/dev/export_tJunction_20040906d/tJunction/schema/autodesa/
> vehic
> lespecification/2004/04/01/VehicleSpecification.xsd
>
> so we have plenty of memory available...
>
> ideas? suggestions?
>
> cheers
> dim
>
> ######################################################################
> DISCLAIMER:
> This email and any attachment may contain confidential information.
> If you are not the intended recipient you are not authorized to copy
> or disclose all or any part of it without the prior written consent
> of Toyota.
>
> Opinions expressed in this email and any attachment are those of the
> sender and not necessarily the opinions of Toyota.
> Please scan this email and any attachment for viruses.
> Toyota does not accept any responsibility for problems
> caused by viruses, whether it is Toyota's fault or not.
> ######################################################################
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: user-help@xmlbeans.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: user-help@xmlbeans.apache.org