Uploaded image for project: 'RiftSaw'
  1. RiftSaw
  2. RIFTSAW-83

Admin console exception when trying to terminate process instance that has terminated due to process definition being undeployed


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.0-M1
    • Fix Version/s: 2.0-M2
    • Component/s: Console
    • Labels:


      If the user removes a process definition, i.e. removes the jar from the deploy directory, they will get an exception if they attempt to terminate the process through the management console.

      Exception occured: java.lang.RuntimeException: Invocation of method terminate in management interface failed: The process "


      PurchaseGoodsProcess_Store-17" does not exist.[object Element]

      It seem like either

      a) removing a process definition should terminate all instances
      b) you should be able to terminate a process instance whose process definition no longer exists.

      A larger issue is that is related is around the deployment strategy. Deploying a process definition as a jar is odd; I don't know of another BPM product that works this way. Typically, a process definition is a record in a database; if you want to create a new version, then a new record is added to the database. If you want to remove a process definition, then a row is deleted from the database. Process instances are also records in the database; if they require process definitions, then referential integrity is used to make certain the process instances are also deleted with the associated process definitions.

      In this case it appears that process definitions can be deleted (the jars removed or replaced), but the process instances still exist in the database.

        Gliffy Diagrams




              • Assignee:
                objectiser Gary Brown
                jeffdelong Jeff DeLong
              • Votes:
                0 Vote for this issue
                0 Start watching this issue


                • Created: