Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
Date: Fri, 07 Mar 2008 09:56:55 +0100
From: John Embretsen <John.Embretsen@Sun.COM>
Subject: Re: "ant javadoc" on trunk?
In-reply-to: <47D09185.5050706@gmail.com>
Sender: John.Embretsen@Sun.COM
To: derby-dev@db.apache.org
Reply-to: derby-dev@db.apache.org
Message-id: <47D10357.2050902@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
References: <47D07C9E.9070105@gmail.com> <47D07EC8.4080406@gmail.com>
 <47D083B7.7030503@sun.com> <47D088CB.1030507@gmail.com>
 <47D08ED8.5030202@sun.com> <47D08FD3.6050506@sun.com>
 <47D09185.5050706@gmail.com>
User-Agent: Thunderbird 2.0.0.12 (X11/20080228)

Army wrote:
> Narayanan wrote:
>>> I just let it stay and went to make my cup of coffee and on returning 
>>> I found this (about half an hour I guess)
>>>
>>> [javadoc] java.lang.OutOfMemoryError: Java heap space
> 
> [snip]
> 
>> It just keeps going, I am continuously getting
>>
>> java.lang.OutOfMemoryError: Java heap space
> 
> Okay, that corresponds to what I see on one of my test machines, as 
> well.  So this does not appear to be a problem with me 
> specifically...(whew).
> 
> Thank you very much for taking the time to verify!  I'll wait a short 
> while to see if anyone on the list points out something that might 
> resolve this; if not, I guess I'll file a Jira for it...

I see that some of the javadoc targets in build.xml include:

additionalparam="-J-mx320M"

The javadoc build works for me when I add this to the "testing-javadoc" target 
as well. A quick look with JConsole indicates that the testing-javadoc JVM needs 
about 86 MB of heap space (on many systems the default is 64 MB).

-- 
John