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

Duplicate correlationkeyid while executing reusable subprocess through parallel gateway

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • 7.12.0.GA
    • jBPM Core
    • None
    • False
    • None
    • False
    • Hide
      • Build kjar from attached project and upload kjar to maven repository.
      • Configure kie-server with external DB(ex. postgresql or Oracle).
      • Create kie-container with Per_Request runtime strategy and try to start process instance using below API:

       

      KieInternalServices services = KieInternalServices.Factory.get();
CorrelationKeyFactory factory = services.newCorrelationKeyFactory();
CorrelationKey key = factory.newCorrelationKey(String.valueOf(new Date()));
Long pid =
kieServicesClient.
getServicesClient(ProcessServicesClient.class).startProcess(CONTAINER_ID, PROCESS_ID,key);

       - The process successfully finishes but exception logged during process execution.

      Show
      Build kjar from attached project and upload kjar to maven repository. Configure kie-server with external DB(ex. postgresql or Oracle). Create kie-container with Per_Request runtime strategy and try to start process instance using below API:   KieInternalServices services = KieInternalServices.Factory.get(); CorrelationKeyFactory factory = services.newCorrelationKeyFactory(); CorrelationKey key = factory.newCorrelationKey( String .valueOf( new Date())); Long pid = kieServicesClient. getServicesClient(ProcessServicesClient.class).startProcess(CONTAINER_ID, PROCESS_ID,key);  - The process successfully finishes but exception logged during process execution.
    • ---
    • ---
    • 2022 Week 41-43 (from Oct 10), 2022 Week 44-46 (from Oct 31), 2022 Week 47-49 (from Nov 21), 2022 Week 50-02 (from Dec 12)

    Description

      Duplicate correlationkeyid while executing reusable subprocess through parallel gateway. This issue is reproducible only when we use PER_REQUEST strategy with executor enabled and with external DB(postgresql,Mysql,Oracle).

       

       

      10:30:58,183 INFO  [stdout] (Thread-3 (ActiveMQ-client-global-threads)) Dummy2
10:30:58,248 WARN  [org.drools.persistence.PersistableRunner] (Thread-2 (ActiveMQ-client-global-threads)) Could not commit session: org.jbpm.workflow.instance.WorkflowRuntimeException: [DuplicateIssue.DuplicateIdIssue:101 - Parallel Task 1:7] -- CorrelationKey [name=fff:ff:DuplicateIssue.Dummy1:aa1e3c24-ff8f-4b32-b06b-f5c292c1b789, properties=[CorrelationPropertyInfo [name=null, value=fff:ff], CorrelationPropertyInfo [name=null, value=DuplicateIssue.Dummy1], CorrelationPropertyInfo [name=null, value=aa1e3c24-ff8f-4b32-b06b-f5c292c1b789]]] already exists
    at org.jbpm.workflow.instance.impl.NodeInstanceImpl.trigger(NodeInstanceImpl.java:212)
    at org.jbpm.workflow.instance.impl.NodeInstanceImpl.triggerNodeInstance(NodeInstanceImpl.java:414)
 

      Complete stack trace attached.

       

      Issue didnt occur with below scenarios:

      • If we use H2 db
      • if we disable executor with Per_Request strategy
      • If we use Per_Process or singleton strategy

      Attachments

        1. Exception
          18 kB
        2. kjar.zip
          83 kB

        Activity

          People

            rhn-support-egonzale Enrique Gonzalez Martinez (Inactive)
            rhn-support-abhumbe Abhijit Humbe
            Gonzalo Muñoz Fernández Gonzalo Muñoz Fernández
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: