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

Process upgrade fails in RHPAM 7.7 if process instance has active timer and its migrated from BPMS 6.4 release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.41.0.Final
    • 7.40.0.Final
    • Migration
    • None
    • NEW
    • NEW
    • Hide
      1. Deploy attached kjar(Project1_ProcessMigrationIssue-1.0.jar) in BPMS 6.4.11 server in business-central.war and start process instance.
      2.  Stop BPMS 6.4.11 server instance, upgrade backend DB(mysql) using attached script(DBUpgrade.sql) to make it compatible with RHPAM 7.7.1
      3. Start RHPAM 7.7.1 instance,  upload Project1_ProcessMigrationIssue-1.0.jar kjar into artifact repository and create container with ID(com.example:Project1_ProcessMigrationIssue:1.0).
      4. Upload new version of kjar(Project1_ProcessMigrationIssue-1.01.jar) which includes the modified process.
      5. Try to migrate process instances those started with BPMS 6.4 release, migration will fail with NPE. Complete stack trace attached.
      Show
      Deploy attached kjar(Project1_ProcessMigrationIssue-1.0.jar) in BPMS 6.4.11 server in business-central.war and start process instance.  Stop BPMS 6.4.11 server instance, upgrade backend DB(mysql) using attached script(DBUpgrade.sql) to make it compatible with RHPAM 7.7.1 Start RHPAM 7.7.1 instance,  upload Project1_ProcessMigrationIssue-1.0.jar kjar into artifact repository and create container with ID(com.example:Project1_ProcessMigrationIssue:1.0). Upload new version of kjar(Project1_ProcessMigrationIssue-1.01.jar) which includes the modified process. Try to migrate process instances those started with BPMS 6.4 release, migration will fail with NPE. Complete stack trace attached.

      Process upgrade fails in RHPAM 7.7 if process instance has active timer and its migrated from BPMS 6.4 release. Process migration fails with NPE:

       

      12:54:21,793 ERROR [org.jbpm.runtime.manager.impl.error.ExecutionErrorHandlerImpl] (default task-8) Unexpected error during processing : java.lang.NullPointerException
       at org.jbpm.runtime.manager.impl.migration.MigrationManager$1.execute(MigrationManager.java:605)
       at org.jbpm.runtime.manager.impl.migration.MigrationManager$1.execute(MigrationManager.java:575)
       at org.drools.core.fluent.impl.PseudoClockRunner.executeBatch(PseudoClockRunner.java:102)
       at org.drools.core.fluent.impl.PseudoClockRunner.executeBatches(PseudoClockRunner.java:69)
       at org.drools.core.fluent.impl.PseudoClockRunner.execute(PseudoClockRunner.java:61)
       at org.drools.core.fluent.impl.PseudoClockRunner.execute(PseudoClockRunner.java:39)
       at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)
       at org.drools.persistence.PersistableRunner$TransactionInterceptor.execute(PersistableRunner.java:597)
       at org.drools.persistence.PersistableRunner$TransactionInterceptor.execute(PersistableRunner.java:563)
       at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)
       at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.internalExecute(OptimisticLockRetryInterceptor.java:102)
       at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.execute(OptimisticLockRetryInterceptor.java:83)
       at org.drools.persistence.jpa.OptimisticLockRetryInterceptor.execute(OptimisticLockRetryInterceptor.java:44)
       at org.drools.core.command.impl.AbstractInterceptor.executeNext(AbstractInterceptor.java:39)
       at org.drools.persistence.jta.TransactionLockInterceptor.execute(TransactionLockIntercep
      

       

            elguardian@gmail.com Enrique González Martínez (Inactive)
            rhn-support-abhumbe Abhijit Humbe
            Karel Suta Karel Suta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: