Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-974

Cli calls leak memory in Host Controller when reading children names in domain mode

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 2.0.0.Beta7
    • None
    • Management, Remoting
    • None
    • Hide
      • Download wildfly-9.0.0.Final.zip
      • Unpack
      • Create a management user
      • Start wildfly using bin/domain.sh
      • Call the script bin/jboss-cli.sh with the command :read-children-names(child-type=host) time and time again, example:
        while true; do jboss-cli.sh --connect --user="myuser" --password="mypassword" --command=":read-children-names(child-type=host)" && sleep 2; done
      • Monitor the jvm and see lots of space taken in eden, propagated to old gen by gc and never getting collected from there
      Show
      Download wildfly-9.0.0.Final.zip Unpack Create a management user Start wildfly using bin/domain.sh Call the script bin/jboss-cli.sh with the command :read-children-names(child-type=host) time and time again, example: while true; do jboss-cli.sh --connect --user="myuser" --password="mypassword" --command=":read-children-names(child-type=host)" && sleep 2; done Monitor the jvm and see lots of space taken in eden, propagated to old gen by gc and never getting collected from there
    • User Experience
    • Workaround Exists
    • Hide

      Use -Djboss.remoting.pooled-buffers=false on the command line to disable the byte buffer pooling.

      Show
      Use -Djboss.remoting.pooled-buffers=false on the command line to disable the byte buffer pooling.

    Description

      Calling the cli using the command:
      jboss-cli.sh --connect --user="myuser" --password="mypassword" --command=":read-children-names(child-type=host)"
      leaks memory to old gen. Eventually the host controller goes OOM if called to often.

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. REM3-208 ByteBuffer leaks via HttpUpgradeConnectionProvider and RemoteConnectionProvider

          • Critical - To be worked on immediately following BLOCKER issues.
          • Resolved
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-283 Memory leak in org.xnio.ByteBufferSlicePool

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dlloyd@redhat.com David Lloyd
              michael.noack Michael Noack (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: