ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 14078] New: - Out of Memory exception while using Jar/Ear/War task
Date Wed, 30 Oct 2002 01:28:41 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14078>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14078

Out of Memory exception while using Jar/Ear/War task

           Summary: Out of Memory exception while using Jar/Ear/War task
           Product: Ant
           Version: 1.5.1
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: bhegr@netdelivery.com


I've read in the user forums that a workaround for the Out of Memory exception 
that crops up with Javac is to use 'fork=true' in the task call.

Our build process does some pretty heavy jar/ear/war building, and the Java 
process that runs Ant eats up a lot of memory when I do this. I've bumped up 
the initial and maximum memory heap but the OOM still pops up.

It would be a helpful enhancement to get the memory cleaned up after a zip 
task, or (better yet) to have a fork option on the zip task so that the 
jar/war/ear tasks that inherit from zip also get the benefit of forking.

I think the workaround I'll try will be to explicitly call the Jar executable 
from an exec or apply task.

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message