Uploaded image for project: 'JBoss BRMS Platform'
  1. JBoss BRMS Platform
  2. RHBRMS-2484

Memory leak in KieScanner

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 6.4.0
    • 6.3.0.GA
    • BRE, Kie-Server
    • DR1
    • Hide

      1. Download and unzip the attached kie-scanner-memleak.zip
      2. cd kie-scanner-memleak/kie-scanner-memleak-kjar
      3. mvn install
      4. Go to BRMS business-central
      5. Create a container for kie-server with groupId="com.sample", artifactId="kie-scanner-memleak-kjar", version="1.0.0-SNAPSHOT"
      6. Start the container
      7. Start scanner with interval "500" ms (or shorter)
      8. Watch the heap via jconsole or gc logging. -> footprint will go up and end up with OOME.

      Show
      1. Download and unzip the attached kie-scanner-memleak.zip 2. cd kie-scanner-memleak/kie-scanner-memleak-kjar 3. mvn install 4. Go to BRMS business-central 5. Create a container for kie-server with groupId="com.sample", artifactId="kie-scanner-memleak-kjar", version="1.0.0-SNAPSHOT" 6. Start the container 7. Start scanner with interval "500" ms (or shorter) 8. Watch the heap via jconsole or gc logging. -> footprint will go up and end up with OOME.

    Description

      Platform JIRA for https://issues.jboss.org/browse/DROOLS-1199

      The issue is also reported from kie-server scanner. I believe that the root cause is the same but I write "Steps to Reproduce" for kie-server case for QA verification.

      Attachments

        Issue Links

          incorporates

          Bug - A problem that impairs or prevents the functions of the product. DROOLS-1199 Memory leak in KieScanner

          • 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
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. RHBRMS-2485 [GSS] (6.3.z) Memory leak in KieScanner

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

          Activity

            People

              mfusco@redhat.com Mario Fusco
              rhn-support-tkobayas Toshiya Kobayashi
              Archiver:
              rhn-support-ceverson Clark Everson
              Jakub Schwan Jakub Schwan
              Jakub Schwan Jakub Schwan

              Dates

                Created:
                Updated:
                Resolved:
                Archived:

                PagerDuty