oom at javadoc time

Henri Gomez henri.gomez at gmail.com
Fri Sep 14 11:26:30 PDT 2012


Did there is a way to define Xmx for javadoc from environment variable ?

2012/9/14 David Holmes <david.holmes at oracle.com>:
> Henri,
>
> 32-bit and 64-bit VMs use different defaults for heap etc. Looks like the
> 32-bit default is too small for this case.
>
> David
>
>
> On 14/09/2012 10:42 PM, Henri Gomez wrote:
>>
>> I see this error when building on CentOS 5 (32bits) on a VM with 2Gb RAM :
>>
>> ../../src/share/classes/java/util/streams/TerminalSink.java:43:
>> warning - @@@ is an unknown tag.
>>
>> ../../src/share/classes/java/util/streams/ops/ShortCircuitTerminalOp.java:46:
>> warning - @return tag has no arguments.
>> ../../src/share/classes/java/util/streams/ops/TerminalOp.java:44:
>> warning - @return tag has no arguments.
>>
>> /home/obuilder/workspace/openjdk8-lambda-standard-build/noarch/centos5-i386-builder/build/linux-i586/impsrc/javax/xml/bind/JAXBContext.java:262:
>> warning - Tag @see: reference not found: S 7.4.1 "Named Packages" in
>> Java Language Specification</a>
>> javadoc: error - java.lang.OutOfMemoryError: Please increase memory.
>> For example, on the JDK Classic or HotSpot VMs, add the option -J-Xmx
>> such as -J-Xmx32m.
>> 1 error
>> 14 warnings
>> make[3]: ***
>> [/home/obuilder/workspace/openjdk8-lambda-standard-build/noarch/centos5-i386-builder/build/linux-i586/docs/api/index.html]
>> Error 1
>> make[3]: Leaving directory
>>
>> `/home/obuilder/workspace/openjdk8-lambda-standard-build/noarch/centos5-i386-builder/jdk/make/docs'
>> make[2]: *** [docs] Error 1
>> make[2]: Leaving directory
>>
>> `/home/obuilder/workspace/openjdk8-lambda-standard-build/noarch/centos5-i386-builder/jdk/make'
>> make[1]: *** [jdk-build] Error 2
>> make[1]: Leaving directory
>>
>> `/home/obuilder/workspace/openjdk8-lambda-standard-build/noarch/centos5-i386-builder'
>> make: *** [build_product_image] Error 2
>> can't find java, build failed
>>
>> I didn't appears on 64bits instances also with 2Gb RAM.
>>
>> Any ideas ?
>>
>


More information about the lambda-dev mailing list