Uploaded image for project: 'Drools'
  1. Drools
  2. DROOLS-4805

Memory leak in STREAM mode (# PointInTimeTriggers growing)

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.29.0.Final
    • Fix Version/s: 7.31.0.Final
    • Component/s: None
    • Labels:
      None
    • Sprint:
      2019 Week 47-49 (from Nov 18)
    • Steps to Reproduce:
      Hide

      I haven't been able to reproduce this problem in isolation yet, but I have access to systems where the problem occurs.

      Show
      I haven't been able to reproduce this problem in isolation yet, but I have access to systems where the problem occurs.
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      When running our engine in STREAM mode, we notice a number of Drools internal object references increasing time even though the fact count stays relatively constant.

      jmap -histo <pid> shows:

       num     #instances         #bytes  class name
      ----------------------------------------------
         1:      17478466     1258449552  java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask
         2:      17475174      699006960  org.drools.core.time.impl.JDKTimerService$JDKJobHandle
         3:      17762331      568394592  java.util.concurrent.ConcurrentHashMap$Node
         4:      17475174      559205568  org.drools.core.rule.SlidingTimeWindow$BehaviorJobContext
         5:      17475174      559205568  org.drools.core.time.impl.DefaultTimerJobInstance
         6:       8596776      551411680  [C
         7:      18898675      453568200  java.lang.Long
         8:      17475174      419404176  org.drools.core.time.SelfRemovalJobContext
         9:      17475174      279602784  org.drools.core.time.SelfRemovalJob
        10:      17475174      279602784  org.drools.core.time.impl.PointInTimeTrigger
        11:       9263698      222328752  java.lang.String
        12:       4584671      146709472  java.util.HashMap$Node
        13:        246658      138804176  [B
      

      These number continue to increase over time until the system OOMs.

      Graph for # of facts in the session looks like:

      The engine is fairly busy - we're constantly adding and removing facts.

      Our rules are available here:
      https://github.com/OpenNMS/opennms/blob/opennms-25.0.0-1/opennms-base-assembly/src/main/filtered/etc/alarmd/drools-rules.d/alarmd.drl#L234

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                mfusco Mario Fusco
                Reporter:
                jesse-4 Jesse White
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: