ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Darin Swanson <Darin_Swan...@us.ibm.com>
Subject RE: Out of memory with javac
Date Tue, 25 May 2004 20:08:41 GMT
It works fine on 1.4.1_07
I have only a certain set of VMs that I can get my hands on due to 
restrictions imposed by my employer :-) so I cannot get 1.4.1_02 or 
1.4.1_03

I was testing on 1.4.2_03. and 1.4.2_04; both fail.


Darins





"Peter Bulford" <pbulford@intellitactics.com>
05/25/2004 12:37 PM
Please respond to "Ant Users List"
 
        To:     "Ant Users List" <user@ant.apache.org>
        cc: 
        Subject:        RE: Out of memory with javac


Hi Darin.

I don't have your answer however I'm curious if your problem works fine on 
1.4.1_02 and does not work on 1.4.1_03.

Pete Bulford <mailto:pbulford@intellitactics.com> 

-----Original Message-----
From: Darin Swanson [mailto:Darin_Swanson@us.ibm.com]
Sent: Tuesday, May 25, 2004 3:10 PM
To: Ant Users List
Subject: RE: Out of memory with javac


Thanks NetaB...but I don't think you helped me at all :-)

I have fork set to be true so memorymaximumsize and memoryinitialsize 
should not be ignored.

The main thrust of my question is why the difference running on the two 
implementations of javac? 
Works fine on 1.3.1, 1.4.1. 
Does not work on 1.4.2? 
I could not find a bug in Sun's bug parade either for this problem with 
javac.

TIA
Darins




"Neta Bar Tal" <NETAB@Amdocs.com>
05/24/2004 09:21 PM
Please respond to "Ant Users List"
 
        To:     "Ant Users List" <user@ant.apache.org>
        cc: 
        Subject:        RE: Out of memory with javac



Hi Darin,
Did you try to run ant with ANT_OPTS set to something like: -Xms1024m
-Xmx1024m
When you pass the flags  memorymaximumsize and memoryinitialsize it is
only used when you set the compiler to run on new JVM and
Is deprecated when you use your default javac.

netaB




-----Original Message-----
From: Darin Swanson [mailto:Darin_Swanson@us.ibm.com]

Sent: Tuesday: May 25: 2004 3:43 AM
To: Ant Users List
Subject: Out of memory with javac

Ant 1.6.1

Running the same buildfile I am seeing different results for using javac
depending on the javac executable I am using.

<javac fork="true" debug="on" memoryinitialsize="200m"

memorymaximumsize="200m" destdir="testingBin" classpath=...> </javac>

Using a 1.4.2 JDK install,  I always run out of memory when the task is
forked and I set memory attributes....and it is not that big of a build.
[javac] The system is out of resources.
[javac] Consult the following stack trace for details.
[javac] java.lang.OutOfMemoryError

Using a 1.3.1 JDK install, exact same buildfile, no out of memory.

It is almost like the -J options passed to the 1.4.2 javac.exe are
ignored?

Is this a known issue? I searched bugzilla but found nothing new enough
to be relevant Is this just dumb user error :-) ?

TIA
Darins


The information contained in this message is proprietary of Amdocs,
protected from disclosure, and may be privileged.
The information is intended to be conveyed only to the designated 
recipient(s)
of the message. If the reader of this message is not the intended 
recipient,
you are hereby notified that any dissemination, use, distribution or 
copying of

this communication is strictly prohibited and may be unlawful.

If you have received this communication in error, please notify us 
immediately
by replying to the message and deleting it from your computer.
Thank you.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org





---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org



Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message