Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5714

JVM options for Fabric managed containers are not aligned

    Details

    • Sprint:
      Sprint 5 - towards ER2
    • Steps to Reproduce:
      Hide

      not needed

      Show
      not needed

      Description

      I noticed a fairly big difference in the JVM arguments used when creating containers in Fabric.

      My root container runs with

      -server -Xms512M -Xmx1024M -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass -XX:PermSize=128M -XX:MaxPermSize=256M
      

      A child container only runs with

      -server
      

      An ssh container uses

      -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass 
      

      What this means:

      • Neither child nor SSH container set -Xmx
      • Neither child nor SSH set -XX:MaxPermSize
      • SSH container does not use -server, hence defaults to client JVM
      • child container does not set -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass, which I thought was needed to work around some dead lock in Karaf.

      I really think an

      • SSH container should run with -server at the least.
      • child and SSH container should explicitly set -Xmx
      • child and SSH container should also set -XX:MaxPermSize

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                oscerd Andrea Cosentino
                Reporter:
                mielket Torsten Mielke
                Tester:
                Andrej Vano
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: