It seems that no matter what memory / cpu limit a karaf pod has, it has always the same java args
$ oc rsh karaf2-camel-log-2-c1nti $ cat /proc/1/cmdline | tr -s '\0' '\n' /usr/lib/jvm/java-1.8.0/bin/java -server -Xms512M -Xmx1024M -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass -Dcom.sun.management.jmxremote -Djava.endorsed.dirs=/usr/lib/jvm/java-1.8.0/jre/lib/endorsed:/usr/lib/jvm/java-1.8.0/lib/endorsed:/deployments/karaf/lib/endorsed -Djava.ext.dirs=/usr/lib/jvm/java-1.8.0/jre/lib/ext:/usr/lib/jvm/java-1.8.0/lib/ext:/deployments/karaf/lib/ext -Dkaraf.instances=/deployments/karaf/instances -Dkaraf.home=/deployments/karaf -Dkaraf.base=/deployments/karaf -Dkaraf.data=/deployments/karaf/data -Dkaraf.etc=/deployments/karaf/etc -Djava.io.tmpdir=/deployments/karaf/data/tmp -Djava.util.logging.config.file=/deployments/karaf/etc/java.util.logging.properties -Djavax.management.builder.initial=org.apache.karaf.management.boot.KarafMBeanServerBuilder -javaagent:/opt/jolokia/jolokia.jar=config=/opt/jolokia/etc/jolokia.properties -Dkaraf.startLocalConsole=false -Dkaraf.startRemoteShell=true -classpath /deployments/karaf/lib/karaf-jaas-boot.jar:/deployments/karaf/lib/karaf-jmx-boot.jar:/deployments/karaf/lib/karaf.jar org.apache.karaf.main.Main
- blocks
-
ENTESB-8803 Karaf container should auto set the JAVA_MAX_MEMORY env var based the max memory allocated to the container
-
- Closed
-
