Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-4403

Orphaned records in the sessionInfo table

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 7.13.2.GA
    • 7.12.1.GA
    • jBPM Core
      • Red Hat Process Automation Manager (RHPAM)
    • False
    • None
    • False
    • CR1
    • +
    • Hide

      To reproduce this issue follow the steps below:

       

      1. Import mortgage-process project from RHPAM samples;
      2. Change the actor for each human task in the business process;
      3. Deploy mortgage-process project;
      4. Start the project and check the content of the following three tables: processInstanceInfo, contextMappingInfo and sessionInfo;
      5. Confirm that they contain one new record each that points to the newly started process instance;
      6. Start the first human task and once the task is finished check the content of the sessionInfo table - it will contain 2 more records. However, contextMappingInfo will not be changed and there will still be only one record as a connection between sessionInfo and processInstanceInfo;
      7. Continue execution of the process instance and upon its completion check and confirm that relevant records were removed from processInstanceInfo and contextMappingInfo. From the sessionInfo table only initially created record is removed and all other records that were created during process instance execution are orphaned and they will stay in the table. 
      Show
      To reproduce this issue follow the steps below:   Import mortgage-process project from RHPAM samples; Change the actor for each human task in the business process; Deploy mortgage-process project; Start the project and check the content of the following three tables: processInstanceInfo, contextMappingInfo and sessionInfo; Confirm that they contain one new record each that points to the newly started process instance; Start the first human task and once the task is finished check the content of the sessionInfo table - it will contain 2 more records. However, contextMappingInfo will not be changed and there will still be only one record as a connection between sessionInfo and processInstanceInfo; Continue execution of the process instance and upon its completion check and confirm that relevant records were removed from processInstanceInfo and contextMappingInfo. From the sessionInfo table only initially created record is removed and all other records that were created during process instance execution are orphaned and they will stay in the table. 
    • ---
    • ---
    • 2022 Week 29-31 (from Jul 18), 2022 Week 32-34 (from Aug 8), 2022 Week 35-37 (from Aug 29), 2022 Week 38-40 (from Sept 19), 2022 Week 41-43 (from Oct 10), 2022 Week 44-46 (from Oct 31)

      According to our documentation, when a process instance is executed using "PER_PROCESS_INSTANCE" runtime strategy, relevant record(s) should be removed from the sessionInfo table upon the process instance completion. However, a number of records get created in the sessionInfo table every time a human task is performed but they do not get removed after the process instance is completed. This causes the number of records to get increased very quickly in the sessionInfo table. 
       

        1. mySpace_project.zip
          79 kB

              rhn-support-egonzale Enrique Gonzalez Martinez (Inactive)
              rhn-support-bkramer1 Biljana Kramer
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: