Hi,

I just recently upgraded from Ant 1.3 to Ant 1.4.1. I am now consistently
getting OutOfMemoryError exceptions when building a large java project with
<javac> on Unix machines through Ant 1.4.1 and Tomcat 3.2.1. I am using
Tomcat for our Servlet-based build application, which allows users to kick
off builds on various machines through HTTP requests. I do not encounter the
out of memory error when invoking Ant and building the projects from the
command line. I also do not encounter the out of memory error when building
through Ant 1.3 and Tomcat 3.2.1.

I have read through the mailing list and FAQs and tried implementing many of
the helpful suggestions for fixing OutOfMemoryError exceptions, including
varying and increasing the heap size through the ANT_OPTS environment
variable and <javac> memoryMaximumSize attribute, but none of them seem to
work. I have also tried passing more memory to the JVM when starting Tomcat
using the TOMCAT_OPTS variable. The ANT_OPTS and memoryMaximumSize attribute
syntaxes I'm using are:

setenv ANT_OPTS "-Xms128m -Xmx512m"

<javac srcdir="${SharedSourceDir}" destdir="${SharedDeployDir}"
debug="${debug}" memoryMaximumSize="512m">
  <classpath refid="project.class.path"/>
  <exclude name="Web/**/*.*"/>
  <exclude name="ejbcgen/**/*.*"/>
</javac>

Please note that I'm not using fork="yes" in the <javac> task because I
thought it was no longer required in Ant 1.4.1. Please correct me if I'm
wrong in interpreting this fix in the WHAT'S NEW documentation.

I would really like to stick with Ant 1.4.1 as it provides the parallel
processing that is needed in building other projects.

Thank you very much in advance to everyone who can help me resolve this
issue.

-Nathan

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to