Thanks all!
It appears that raising the max memory in the javac task did the trick.
Petar Tahchiev wrote:
>
> On 25/08/06, lfleal <[EMAIL PROTECTED]> wrote:
>>
>> David,
>>
>> The same build script works just fine under 1.5 on a win 32 server, the
>> only
>> difference is that on the new serv
Corley (AT/LMI) [mailto:[EMAIL PROTECTED]
Sent: 25 August 2006 13:05
To: Ant Users List
Subject: RE: OutOfMemoryError when building on x64
Hey Lewis,
I found the following
http://forum.java.sun.com/thread.jspa?threadID=671184&messageID=3928329
in which they detail a similar situa
On 25/08/06, lfleal <[EMAIL PROTECTED]> wrote:
David,
The same build script works just fine under 1.5 on a win 32 server, the only
difference is that on the new server, the x64 version of the 1.5 JDK is
used. The ant options are set to a max heap of 512m (where the old server
uses the default
es any difference in the x64
machine.
-Original Message-
From: lfleal [mailto:[EMAIL PROTECTED]
Sent: 25 August 2006 12:36
To: user@ant.apache.org
Subject: RE: OutOfMemoryError when building on x64
David,
The same build script works just fine under 1.5 on a win 32 server, the
only diffe
David,
The same build script works just fine under 1.5 on a win 32 server, the only
difference is that on the new server, the x64 version of the 1.5 JDK is
used. The ant options are set to a max heap of 512m (where the old server
uses the default). There seems to be more going on here...
Dav
You should set the -Xms -Xmx properties for your JVM. They control the
minimum and maximum heap size the JVM is allowed to use. There's plenty
of documentation for these two switches online.
-Original Message-
From: lfleal [mailto:[EMAIL PROTECTED]
Sent: 25 August 2006 03:17
To: user@ant
