Even after the fork=true change (last check out was yesterday or today), I'm
continuing to get out of memory errors on the build.
I'm using a 350 mhz PC with windows 2k and 384M ram.
I've tried adding -Xmx228m to
- tools/bin/ant,
- on the build command line as -D option, and
- as a JAVA_OPTS environment variable
with no effect.
Tracking memory usage, it seems the java process is only using about 84 meg
when it dies (around the -swf-block-project/jfor-block stage) which means
maybe I've not found the right way to make more memory available.
Any advice? Are there others with similar setups having/not having
problems?
-Geoff Howard
The tail end of the console output is below.
-swf-block-project-samples:
filter-jdbc:
nofilter-jdbc:
prepare-jdbc:
prepare-database-connection-pw:
prepare-database-connection-no-pw:
prepare-database-connection:
-swf-block-project:
[roles-tool] Reading:
D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\cocoon\
cocoon.roles
[roles-tool] No Changes:
D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\coco
on\cocoon.roles
[echo] Compiling block with Java 1.4, debug on, optimize off,
deprecation o
ff...
[javac] Since fork is true, ignoring compiler setting.
jfor-block:
BUILD FAILED
java.lang.OutOfMemoryError
Total time: 5 minutes 1 second
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
