On 14/07/06, Noel Sebastien (BIL) <[EMAIL PROTECTED]> wrote:
Thanks... We are running on a WEbApp under WebSphere 5.1. I already set
memory to 512 Mo and printed the free memory before the Ant call. 300 Mo
free is displayed !! I hoped it was enough !!!
We call an Ant file containing some tasks (easy OR heavy ones) ..
Sometimes it crashes on an easy FTP task.. Sometimes on an heavy javac
... The probem seems to be not related to the task involved.
Thanks for the suggestion.. I am now upgraded to 1.6.5. We cross the
fingers and wait ....
-----Original Message-----
From: Petar Tahchiev [mailto:[EMAIL PROTECTED]
Sent: vendredi 14 juillet 2006 09:18
To: Ant Users List
Subject: Re: OutOfMemoryError while running Ant from Java call.
On 13/07/06, Noel Sebastien (BIL) <[EMAIL PROTECTED]> wrote:
> Does anyone encounter any same kind of my problem ?
> We are running an JVM application that call Ant within Java ? Am I
> calling Ant in a wrong way ? Does anyone has a good reference for an
> accurate Java call to Ant.
> It is Ant 1.6.2. Exception occurred once in a while, namely not on the
> same targets. Very strange behavior indeeed.
>
> /APPLICATIONS/prism/PrismResources/WF_depl_on_platform/scripts/earAntB
> ui
> ld.xml:649: java.lang.OutOfMemoryError
> at
> org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:131)
> at
> org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
> at org.apache.tools.ant.Task.perform(Task.java:364)
> at org.apache.tools.ant.Target.execute(Target.java:341)
> at org.apache.tools.ant.Target.performTasks(Target.java:369)
> at
org.apache.tools.ant.Project.executeTarget(Project.java:1214)
> at
> org.apache.tools.ant.Project.executeTargets(Project.java:1062)
> at
> com.dexiabil.prism.apre.ant.OurAntMain.runBuild(OurAntMain.java:485)
> at
> com.dexiabil.prism.apre.ant.OurAntMain.startAnt(OurAntMain.java:252)
> at
> com.dexiabil.prism.apre.ant.OurAntMain.startAnt(OurAntMain.java:204)
> at com.dexiabil.prism.apre.ant.OurAnt.startAnt(OurAnt.java:41)
> at
com.dexiabil.prism.apre.agent.AntAgent.use(AntAgent.java:131)
> at
> com.dexiabil.prism.bpm.call.AsyncCall$UsageThread.run(AsyncCall.java:1
> 15
> )
> Caused by: java.lang.OutOfMemoryError
> --- Nested Exception ---
> java.lang.OutOfMemoryError
>
> Thnak you in advance
> Sebastien
>
> ---------------------
> An electronic message is not binding on its sender.
> Any message referring to a binding engagement must be confirmed in
writing and duly signed.
> ---------------------
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
> commands, e-mail: [EMAIL PROTECTED]
>
>
The only that comes in my mind is that you can try increasing java heap
space. When you start your application that calls ant try specifying
this
java -Xms256m
or try to allocate more memory.
By the way, what kind of stuff are you trying to build with ant, and
also you may consider updgrading to Ant 1.6.5.
--
Regards, Petar!
Karlovo, Bulgaria.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in
writing and duly signed.
---------------------
---------------------
An electronic message is not binding on its sender.
Any message referring to a binding engagement must be confirmed in writing and
duly signed.
---------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I am not familiar with WebSphere, but I have technical experience
with both JBoss and WebLogic. On both these servers I had the same
problem when trying to redeploy in the hotdeploy directory a large
application - Java Heap Space Exception was thrown. Althogh I think
your situation is quite different, for we used Hibernate
Object-relational mapping and I kind of thought that the problem was
there.....
Anyway, my opinion is that this is not ant-related problem but more
like websphere one. To be completely sure: try running your ant
scripts on the prompt? Also is the project you are trying to build
large? And my last guess is: if it is possible try running the project
on another server.
P.S. Check to see if use the java task in your build.xml and if you
use the fork attribute, also check the junit tests(if present) and set
the fork attribute so that the opertions to be forked to a new JVM.
Hope this helped.
--
Regards, Petar!
Karlovo, Bulgaria.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
