Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-283

Memory leak in org.xnio.ByteBufferSlicePool

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.0.DR10
    • 7.0.0.DR3
    • Management, Remoting
    • None
    • Workaround Exists
    • Hide

      For a workaround, if this problem still occurs, set the following system property: -Djboss.remoting.pooled-buffers=false

      This will use regular GC to manage buffers at a slight performance cost.

      Show
      For a workaround, if this problem still occurs, set the following system property: -Djboss.remoting.pooled-buffers=false This will use regular GC to manage buffers at a slight performance cost.
    • Hide

      ModelControllerClient is used for client requests, OOM appears in a minute.

      JBOSS_HOME=`realpath jboss-eap-7.0`
cd leak-test
mvn test -Djboss.dist=$JBOSS_HOME -Dtest=ControllerClientTestCase

      JBoss-cli running in a modular classloading environment (jboss-cli.sh) is used for client requests, it took some time for OOM to appear.

      JBOSS_HOME=`realpath jboss-eap-7.0`
cd leak-test
mvn test -Djboss.dist=$JBOSS_HOME -Dtest=MultipleClientsTestCase

      For manual server lifecycle management just comment out @Before and @After annotations in org.jboss.qa.CLITestBase.java

      Show
      ModelControllerClient is used for client requests, OOM appears in a minute. JBOSS_HOME=`realpath jboss-eap-7.0` cd leak-test mvn test -Djboss.dist=$JBOSS_HOME -Dtest=ControllerClientTestCase JBoss-cli running in a modular classloading environment (jboss-cli.sh) is used for client requests, it took some time for OOM to appear. JBOSS_HOME=`realpath jboss-eap-7.0` cd leak-test mvn test -Djboss.dist=$JBOSS_HOME -Dtest=MultipleClientsTestCase For manual server lifecycle management just comment out @Before and @After annotations in org.jboss.qa.CLITestBase.java

    Description

      Repetitive management requests on EAP leads to OOM exception.

      Attachments

        1. jconsole.png
          jconsole.png
          74 kB
        2. leak-test.zip
          13 kB
        3. usage.png
          usage.png
          76 kB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-974 Cli calls leak memory in Host Controller when reading children names in domain mode

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

          Bug - A problem that impairs or prevents the functions of the product. REM3-200 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-736 Memory leak in server management controller

          • 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.
          • Resolved

          Activity

            People

              dlloyd@redhat.com David Lloyd
              pkremens@redhat.com Petr Kremensky (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: