You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Geoff Howard <co...@leverageweb.com> on 2003/01/22 06:26:53 UTC
out of memory still building cvs
Even after the fork=true change (last check out was yesterday or today), I'm
continuing to get out of memory errors on the build.
I'm using a 350 mhz PC with windows 2k and 384M ram.
I've tried adding -Xmx228m to
- tools/bin/ant,
- on the build command line as -D option, and
- as a JAVA_OPTS environment variable
with no effect.
Tracking memory usage, it seems the java process is only using about 84 meg
when it dies (around the -swf-block-project/jfor-block stage) which means
maybe I've not found the right way to make more memory available.
Any advice? Are there others with similar setups having/not having
problems?
-Geoff Howard
The tail end of the console output is below.
-swf-block-project-samples:
filter-jdbc:
nofilter-jdbc:
prepare-jdbc:
prepare-database-connection-pw:
prepare-database-connection-no-pw:
prepare-database-connection:
-swf-block-project:
[roles-tool] Reading:
D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\cocoon\
cocoon.roles
[roles-tool] No Changes:
D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\coco
on\cocoon.roles
[echo] Compiling block with Java 1.4, debug on, optimize off,
deprecation o
ff...
[javac] Since fork is true, ignoring compiler setting.
jfor-block:
BUILD FAILED
java.lang.OutOfMemoryError
Total time: 5 minutes 1 second
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: out of memory still building cvs
Posted by Konstantin Piroumian <kp...@apache.org>.
From: "Jeff Turner" <je...@apache.org>
> On Wed, Jan 22, 2003 at 12:26:53AM -0500, Geoff Howard wrote:
> > Even after the fork=true change (last check out was yesterday or today),
I'm
> > continuing to get out of memory errors on the build.
> >
> > I'm using a 350 mhz PC with windows 2k and 384M ram.
> > I've tried adding -Xmx228m to
> > - tools/bin/ant,
> > - on the build command line as -D option, and
> > - as a JAVA_OPTS environment variable
> > with no effect.
>
> Setting ANT_OPTS is the right way to do it, I think.
>
> set ANT_OPTS=-Xmx228m
>
> > Tracking memory usage, it seems the java process is only using about 84
meg
> > when it dies (around the -swf-block-project/jfor-block stage) which
means
> > maybe I've not found the right way to make more memory available.
> >
> > Any advice? Are there others with similar setups having/not having
> > problems?
The same problem here when 'webapp' target is used.
PIV 2.4Ghz, 512Mb RAM, Win2000
>
> I've built Cocoon a couple of times today without problems, using
> './build.sh -Dinclude.webapp.libs=yes webapp-local'. This is with
> JDK1.4.1 on Debian.
webapp-local target works fine for me too. Try 'webapp' target instead.
See also my previous posting about setting build properties to suppress
JavaDoc and documentation generation. I've asked that to lower the memory
consumption and build time.
--
Konstantin
>
>
> --Jeff
>
> > -Geoff Howard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: out of memory still building cvs
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Stefano Mazzocchi dijo:
> Geoff Howard wrote:
>
>> Is there a general level of comfort that the build requires this much
>> memory??
>
> I'm personally not that comfortable (expecially since I only have 192Mb
> on my machine and can't even upgrade it anymore :/) but the cocoon build
> system is huge and very complex so it doesn't surprise me that it needs
> that much memory.
today morning I was checking how much memmory it requieres on my Red Hat
Linux 8.0 machine. Using the Linux command "top" it goes to the maximum on
javadocs compiles. There was 2 process running that together used almost
230MB. Every process used 50% of this number.
Maybe it can helps.
Best Regards,
Antonio Gallardo.
>
> but any patch that will lower memory use will be appreciated.
>
> --
> Stefano Mazzocchi <st...@apache.org>
> --------------------------------------------------------------------
>
>
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [PATCH] Re: out of memory still building cvs
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Pier Fumagalli wrote:
> On 23/1/03 19:09, "Stefano Mazzocchi" <st...@apache.org> wrote:
>
>>Geoff Howard wrote:
>>
>>
>>>Is there a general level of comfort that the build requires this much
>>>memory??
>>
>>I'm personally not that comfortable (expecially since I only have 192Mb
>>on my machine and can't even upgrade it anymore :/) but the cocoon build
>>system is huge and very complex so it doesn't surprise me that it needs
>>that much memory.
>>
>>but any patch that will lower memory use will be appreciated.
>
>
> Two stages patch (verified on my box locally, so that might not help in all
> cases): apply the attached patch to build.xml, and update the ant libraries
> to 1.5.1.
>
> Worked for me...
The patch does not lower max memory consumption on W2k JDK1.4.1
I had not forked all tasks that could because in some cases max memory
usage actually grew, and in others it was neglible. I've applied your
patch anyway since in the future these tasks could higher memory usage.
I've also tried running the build using Ant CVS version, and the memory
consumption is a bit lower, so I committed latest Ant. The funny fact is
that if I use my installed centipede version I use less memory than
using build.bat...
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[vote] Commit access back for Pier
Posted by Stefano Mazzocchi <st...@apache.org>.
Pier Fumagalli wrote:
> On 23/1/03 19:09, "Stefano Mazzocchi" <st...@apache.org> wrote:
>
>
>>Geoff Howard wrote:
>>
>>
>>>Is there a general level of comfort that the build requires this much
>>>memory??
>>
>>I'm personally not that comfortable (expecially since I only have 192Mb
>>on my machine and can't even upgrade it anymore :/) but the cocoon build
>>system is huge and very complex so it doesn't surprise me that it needs
>>that much memory.
>>
>>but any patch that will lower memory use will be appreciated.
>
>
> Two stages patch (verified on my box locally, so that might not help in all
> cases): apply the attached patch to build.xml, and update the ant libraries
> to 1.5.1.
>
> Worked for me...
I'm lazy.
What about resorting your commit access so you can do it yourself?
I mean, you were the one who wrote the first Cocoon2 code in the first
place and you are working to patch cocoon for jetty stuff. I don't want
to be flooded with your patches :)
People, what do you think?
--
Stefano Mazzocchi <st...@apache.org>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[PATCH] Re: out of memory still building cvs
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 23/1/03 19:09, "Stefano Mazzocchi" <st...@apache.org> wrote:
> Geoff Howard wrote:
>
>> Is there a general level of comfort that the build requires this much
>> memory??
>
> I'm personally not that comfortable (expecially since I only have 192Mb
> on my machine and can't even upgrade it anymore :/) but the cocoon build
> system is huge and very complex so it doesn't surprise me that it needs
> that much memory.
>
> but any patch that will lower memory use will be appreciated.
Two stages patch (verified on my box locally, so that might not help in all
cases): apply the attached patch to build.xml, and update the ant libraries
to 1.5.1.
Worked for me...
Pier
Re: out of memory still building cvs
Posted by Stefano Mazzocchi <st...@apache.org>.
Geoff Howard wrote:
> Is there a general level of comfort that the build requires this much
> memory??
I'm personally not that comfortable (expecially since I only have 192Mb
on my machine and can't even upgrade it anymore :/) but the cocoon build
system is huge and very complex so it doesn't surprise me that it needs
that much memory.
but any patch that will lower memory use will be appreciated.
--
Stefano Mazzocchi <st...@apache.org>
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: out of memory still building cvs
Posted by Geoff Howard <co...@leverageweb.com>.
Thanks, everyone. It worked for me too with ANT_OPTS set
to -Xms100m -Xmx228m (strange since altering tools/bin/ant should have done
the same thing, but oh well)
I didn't yet disable doc generation (although I didn't notice docs messages
in
the build but I may have dozed off there ;) )
It also seemed validation was kicking the memory up and not releasing it.
Is there a way to "fork" the validation process like the blocks? I'll
probably
disable it next time.
Is there a general level of comfort that the build requires this much
memory??
Geoff
> -----Original Message-----
> From: Gernot Koller [mailto:grizzly@gmx.at]
> Sent: Wednesday, January 22, 2003 4:45 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: out of memory still building cvs
>
>
> Thanks Jeff!
>
> setting ANT_OPTS to "-Xms100m -Xmx400m" did the job for me!
>
> Gernot.
>
> 22-Jan-03 07:05:10, Jeff Turner <je...@apache.org> wrote:
>
> >On Wed, Jan 22, 2003 at 12:26:53AM -0500, Geoff Howard wrote:
> >> Even after the fork=true change (last check out was yesterday
> or today), I'm
> >> continuing to get out of memory errors on the build.
> >>
> >> I'm using a 350 mhz PC with windows 2k and 384M ram.
> >> I've tried adding -Xmx228m to
> >> - tools/bin/ant,
> >> - on the build command line as -D option, and
> >> - as a JAVA_OPTS environment variable
> >> with no effect.
> >
> >Setting ANT_OPTS is the right way to do it, I think.
> >
> >set ANT_OPTS=-Xmx228m
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[PATCH] Re: out of memory still building cvs
Posted by Pier Fumagalli <pi...@betaversion.org>.
Patch (stupid patch) to the build.sh for unix I use to build on OS/X
Pier
"Gernot Koller" <gr...@gmx.at> wrote:
> Thanks Jeff!
>
> setting ANT_OPTS to "-Xms100m -Xmx400m" did the job for me!
>
> Gernot.
>
> 22-Jan-03 07:05:10, Jeff Turner <je...@apache.org> wrote:
>
>> On Wed, Jan 22, 2003 at 12:26:53AM -0500, Geoff Howard wrote:
>>> Even after the fork=true change (last check out was yesterday or today), I'm
>>> continuing to get out of memory errors on the build.
>>>
>>> I'm using a 350 mhz PC with windows 2k and 384M ram.
>>> I've tried adding -Xmx228m to
>>> - tools/bin/ant,
>>> - on the build command line as -D option, and
>>> - as a JAVA_OPTS environment variable
>>> with no effect.
>>
>> Setting ANT_OPTS is the right way to do it, I think.
>>
>> set ANT_OPTS=-Xmx228m
>>
Re: out of memory still building cvs
Posted by Gernot Koller <gr...@gmx.at>.
Thanks Jeff!
setting ANT_OPTS to "-Xms100m -Xmx400m" did the job for me!
Gernot.
22-Jan-03 07:05:10, Jeff Turner <je...@apache.org> wrote:
>On Wed, Jan 22, 2003 at 12:26:53AM -0500, Geoff Howard wrote:
>> Even after the fork=true change (last check out was yesterday or today), I'm
>> continuing to get out of memory errors on the build.
>>
>> I'm using a 350 mhz PC with windows 2k and 384M ram.
>> I've tried adding -Xmx228m to
>> - tools/bin/ant,
>> - on the build command line as -D option, and
>> - as a JAVA_OPTS environment variable
>> with no effect.
>
>Setting ANT_OPTS is the right way to do it, I think.
>
>set ANT_OPTS=-Xmx228m
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: out of memory still building cvs
Posted by Jeff Turner <je...@apache.org>.
On Wed, Jan 22, 2003 at 12:26:53AM -0500, Geoff Howard wrote:
> Even after the fork=true change (last check out was yesterday or today), I'm
> continuing to get out of memory errors on the build.
>
> I'm using a 350 mhz PC with windows 2k and 384M ram.
> I've tried adding -Xmx228m to
> - tools/bin/ant,
> - on the build command line as -D option, and
> - as a JAVA_OPTS environment variable
> with no effect.
Setting ANT_OPTS is the right way to do it, I think.
set ANT_OPTS=-Xmx228m
> Tracking memory usage, it seems the java process is only using about 84 meg
> when it dies (around the -swf-block-project/jfor-block stage) which means
> maybe I've not found the right way to make more memory available.
>
> Any advice? Are there others with similar setups having/not having
> problems?
I've built Cocoon a couple of times today without problems, using
'./build.sh -Dinclude.webapp.libs=yes webapp-local'. This is with
JDK1.4.1 on Debian.
--Jeff
> -Geoff Howard
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: out of memory still building cvs
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi Geoff!
I was the same problem before. But currently it works fine for me.
My config is 512 MB RAM
Red Hat Linux 8.0 (full patched).
I think the top of the mem usage in my environment is 130 MB for building.
Antonio Gallardo
Geoff Howard dijo:
> Even after the fork=true change (last check out was yesterday or today),
> I'm continuing to get out of memory errors on the build.
>
> I'm using a 350 mhz PC with windows 2k and 384M ram.
> I've tried adding -Xmx228m to
> - tools/bin/ant,
> - on the build command line as -D option, and
> - as a JAVA_OPTS environment variable
> with no effect.
>
> Tracking memory usage, it seems the java process is only using about 84
> meg when it dies (around the -swf-block-project/jfor-block stage) which
> means maybe I've not found the right way to make more memory available.
>
> Any advice? Are there others with similar setups having/not having
> problems?
>
> -Geoff Howard
>
> The tail end of the console output is below.
>
> -swf-block-project-samples:
>
> filter-jdbc:
>
> nofilter-jdbc:
>
> prepare-jdbc:
>
> prepare-database-connection-pw:
>
> prepare-database-connection-no-pw:
>
> prepare-database-connection:
>
> -swf-block-project:
> [roles-tool] Reading:
> D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\cocoon\
> cocoon.roles
> [roles-tool] No Changes:
> D:\cvs\xml-cocoon2\build\cocoon\classes\org\apache\coco
> on\cocoon.roles
> [echo] Compiling block with Java 1.4, debug on, optimize off,
> deprecation o
> ff...
> [javac] Since fork is true, ignoring compiler setting.
>
> jfor-block:
>
> BUILD FAILED
> java.lang.OutOfMemoryError
>
> Total time: 5 minutes 1 second
>
>
> --------------------------------------------------------------------- To
> unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org