Uploaded image for project: 'jBPM'
  1. jBPM
  2. JBPM-5255

'Process Not Found' when deploying more than one DeploymentUnit in BPM Suite 6.3 using PER REQUEST strategy

    Details

    • Steps to Reproduce:
      Hide

      1) Download reproducer, it contains KJARs and the project to replicate the issue.

      2) Deploy the kjars to maven, e.g:

      mvn install:install-file -Dfile=sampleProject-1.0.jar -DgroupId=sampleOU -DartifactId=sampleProject -Dversion=1.0 -Dpackaging=jar
      mvn install:install-file -Dfile=sampleProject-1.1.jar -DgroupId=sampleOU -DartifactId=sampleProject -Dversion=1.1 -Dpackaging=jar

      3) Download my app and run the Showcase class which includes main method. Make sure it is pointing to right deployment unit files.

      Result: It will throw a "Process not found" when trying to retrieve the process definition from second deployment unit as the KieSession is the same for both.

      Show
      1) Download reproducer, it contains KJARs and the project to replicate the issue. 2) Deploy the kjars to maven, e.g: mvn install:install-file -Dfile=sampleProject-1.0.jar -DgroupId=sampleOU -DartifactId=sampleProject -Dversion=1.0 -Dpackaging=jar mvn install:install-file -Dfile=sampleProject-1.1.jar -DgroupId=sampleOU -DartifactId=sampleProject -Dversion=1.1 -Dpackaging=jar 3) Download my app and run the Showcase class which includes main method. Make sure it is pointing to right deployment unit files. Result: It will throw a "Process not found" when trying to retrieve the process definition from second deployment unit as the KieSession is the same for both.
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use Per Process Instance.

      Show
      Use Per Process Instance.
    • Docs QE Status:
      NEW
    • QE Status:
      NEW

      Description

      When more than one deployment unit is deployed, the processes definition in the second deployment is not found.

      The issue is that the same ksession is used when deploying and creating a RuntimeManager from different deployment units. The RuntimeManager is different though.

      It happens for Per Request strategy, but works well for Per Process Instance.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  swiderski.maciej Maciej Swiderski
                  Reporter:
                  swiderski.maciej Maciej Swiderski
                  Tester:
                  Tibor Zimanyi
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: