ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Moore, Kent" <>
Subject RE: Using ANT via Remote Desktop
Date Thu, 23 Aug 2007 18:37:45 GMT
Every other product works.


I worked with a third person and found they did not have the problem.


So I started looking into differences in the machines.


After a little poking around I determined the difference was the two machines where it wasn't
working had an environment variable (ANT_OPTS=-Xmx1200m) set by default whereas the guy who
could run ANT scripts via Remote Desktop did not have the variable set.


When I unset ANT_OPTS (and when I lowered the value) I was able to run ANT commands remotely.


There was some reason I changed the value from 1000 to 1200 recently, and in retrospect that
lines up pretty well with when I started having the problem remotely.  Amazing how that works!


I still do not understand why it is a problem remotely but not when I am in front of the machine,
but at least I now know what the difference is!






-----Original Message-----
From: [] 
Sent: Thursday, August 23, 2007 2:52 AM
Subject: AW: Using ANT via Remote Desktop


Sounds like a problem with the remote desktop. Ant does not know if it's started "directly"
or "indirectly".


Could you start other programs like Eclipse or NetBeans via remote desktop?





>-----Urspr√ľngliche Nachricht-----

>Von: news [] Im Auftrag von Kent Moore

>Gesendet: Mittwoch, 22. August 2007 18:46


>Betreff: Using ANT via Remote Desktop


>At work I have a fully patched WinXP SP2 machine.


>When in front of the terminal ANT works fine.


>When executing any ANT target remotely via Remote Desktop I receive the

>following message:


>C:\>ant init

>Error occurred during initialization of VM

>Could not reserve enough space for object heap


>The content of the target being run does not matter.  In this 

>case it was about

>as simple as it gets:


><project basedir="." default="init" name="test">

>    <target name="init">

>        <tstamp/>

>    </target>



>I used to be able to do this, now I can't, and I am not the 

>only one in the

>office with the issue.  I assume it involves a Microsoft 

>patch, but have not

>been able to find a resolution.


>The same problem does NOT occur on W2K or W2K3 machines!


>Does anyone have an idea for a work-around outside of using 

>something like

>Netmeeting or VNC?


>Many thanks!




>To unsubscribe, e-mail:

>For additional commands, e-mail:





To unsubscribe, e-mail:

For additional commands, e-mail:


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