Fork me on GitHub
#boot
<
2019-07-05
>
nha00:07:48

I am trying to use java 11.0.3, and now boot package fails to produce a .jar. I see:

Compiling 187/187 last.ns…
Writing pom.xml and pom.properties...
Adding uberjar entries...
Writing my.jar...
Killed
What could Killed indicate here?

alandipert03:07:28

is that on linux? could be the linux oom killer that killed the java process because the machine ran out of memory

alandipert03:07:26

i think there are commands to know for sure if that’s what happened but i don’t know the off-hand

nha09:07:41

hm, it is on circleCI indeed. However I set the env vars

JVM_OPTS: -server -Xmx3200m
      BOOT_JVM_OPTIONS: "-Xms512m -Xmx1512m"

nha09:07:27

(I now realize that Xmx is different - both should be under the 4gb limit though)

nha09:07:14

It happens when I try to update my base docker image on circle ci - the newer one has java 11

nha10:07:23

it does work locally, so I guess it has to do with the CI setting - java 11 for both, ubuntu linux on circle vs osx locally

nha10:07:17

I changed both to -Xmx3200m and it doesn’t seem to make a difference - locally it doesn’t take more than 2GB it seems

nha21:07:31

right it is a return of 137 so OOM 😄

nha21:07:30

I believe I was using boot 2.7.2 and I am now using 2.8.3 - now looking if ther ecould there be an issue where boot doesn’t respect the memory options or the jvm options changed for some reason

nha23:07:41

trying -XX:+UseContainerSupport - doesn’t seem to work sadly