Uploaded image for project: 'Cloud Enablement'
  1. Cloud Enablement
  2. CLOUD-3193

[EAP7.3] -XX:MaxMetaspaceSize is echoed with non EAP defaults

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • EAP7

      java-default-options script, which is sourced during the eap container launch procedure, echoes the jvm defaults which are of different values to EAP ones.

      This might be confusing to the users and may fool the tests which make assertions on container logs (e.g. https://github.com/jboss-container-images/jboss-eap-modules/blob/master/tests/features/7/gc.feature).

      Out of box EAP image log - see the different values for -XX:MaxMetaspaceSize

      INFO Running jboss-eap-7/eap72-openshift image, version 1.0
-XX:+UseParallelOldGC -XX:MinHeapFreeRatio=10 -XX:MaxHeapFreeRatio=20 -XX:GCTimeRatio=4 -XX:AdaptiveSizePolicyWeight=90 
-XX:MaxMetaspaceSize=100m -XX:ParallelGCThreads=2 -Djava.util.concurrent.ForkJoinPool.common.parallelism=2 -XX:CICompilerCount=2 
-XX:+ExitOnOutOfMemoryError
=========================================================================
  JBoss Bootstrap Environment
  JBOSS_HOME: /opt/eap
  JAVA: /usr/lib/jvm/java-1.8.0/bin/java
  JAVA_OPTS:  -server -verbose:gc -Xloggc:/opt/eap/standalone/log/gc.log -XX:+PrintGCDetails -XX:+PrintGCDateStamps 
-XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m 
-XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m ...

      This is an UX issue, not a functional one as the correct value is used.

            yborgess1@redhat.com Yeray Borges Santana
            pkremens@redhat.com Petr Kremensky (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: