Stream: committers
Topic: java error
Craig Newman (Oct 21 2016 at 21:20):
We’re having some issues with checking the build before committing changes to the Immunization resource and saw the following error:
[java] Error occurred during initialization of VM
[java] Could not reserve enough space for 204800KB object heap
Two independent users have seen this error. Does anyone know what this error means?
Craig Newman (Oct 21 2016 at 21:21):
The error occurs very early in the process
Grahame Grieve (Oct 21 2016 at 21:50):
how muc memory do those users have? are they using 32bit or 64bit java?
Melva Peters (Oct 31 2016 at 16:22):
This error had stopped for me when I updated the build.xml as Richard suggested. It's now started again and seems to occur at the step of the validate v3-codesystems. I also noticed that the build.xml file no longer contains
<target name="Publisher" depends="build">
<java
dir="../../../"
classname="org.hl7.fhir.tools.publisher.Publisher"
failonerror="true"
fork="true"
maxmemory="4000m" >
<arg line="${args}"/>
<jvmarg value="-Xmx4000m"/>
<jvmarg value="-Xms4000m"/>
<jvmarg value="-XX:MaxMetaspaceSize=1024m"/>
<jvmarg value="-Djava.awt.headless=true"/>
<classpath refid="org.hl7.fhir.tools.classpath"/>
</java>
</target>
which is what Richard suggested updating. Anyone have any thoughts on what to do? Rebooting only works some of the time.
Richard Ettema (Nov 01 2016 at 01:57):
@Melva Peters I did not commit those changes to the build.xml. Those settings are for my local environment. I do not know if the build server will work with those settings. If you perform a svn update and the build.xml gets overwritten, you will have to apply those settings again.
Melva Peters (Nov 01 2016 at 02:40):
Thanks @Richard Ettema I had updated my local build.xml as well. I must have updated and now when I look at the file, it doesn't even include this section. Can I just add it back on my local version?
Richard Ettema (Nov 01 2016 at 13:36):
Yes. That's what I do.
Last updated: Apr 12 2022 at 19:14 UTC
