Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8147

In-memory H2 database is constantly growing

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Closed
    • Priority: L3 - Default
    • Resolution: Won't Fix
    • Affects Version/s: 7.6.0
    • Fix Version/s: None
    • Component/s: engine
    • Labels:
      None

      Description

      Setup:

      • Camunda Engine 7.6.0
      • Started standalone in a Java command line program for reproducability
      • Database: H2 In-Memory
      • Two BPMNs for reference
        • "Empty": Start is directly connected to end
        • "Receive Task": Receive task blocks execution, receive task is immediately signalled

      Preconditions:

      • Relative high amount of data that is written to the context (100.000 objects with Instants, contained in a List)
      • BPMNs are deployed prior to the run, and not changed during the testing

      Observation:

      • Running the empty.bpmn process 1000 times does not affect the size of the H2 database on the heap (OK)
      • Running the withReceiveTask.bpmn 1000 times let the H2 Database constantly grow on the heap, even if the database is almost empty (NOK)

      Verifications:

      • The test blocks at the end of the execution, to get a heap dump. The heap dump shows the growed "org.h2.engine.Database" object
      • At the end of the program the Webserver of H2 is started, so the tables can be inspected easily. The only data left in the database are the deployed processes itself (OK)

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            robow Robert Wittek
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: