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

ProcessInstanceId reset after server restart

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Blocker
    • None
    • jBPM 6.1.0.Final
    • Persistence
    • Hide

      0. Setup jbpm for MySQL use.
      1. Start jboss.
      2. Complete some processes.
      3. Stop jboss.
      4. Start jboss again.
      5. Complete another process.
      6. See the ProcessInstanceId 1 twice.

      Show
      0. Setup jbpm for MySQL use. 1. Start jboss. 2. Complete some processes. 3. Stop jboss. 4. Start jboss again. 5. Complete another process. 6. See the ProcessInstanceId 1 twice.

    Description

      I use jbpm 6.1 final and jboss 8.1 wildfly and changed the default setup to use MySQL for hibernation. I noticed, that after a server restart the process instance ids start counting from 1, so if you already had some processes completed before the restart, you get a second process with instance id 1.

      Since the creation of the MySQL table "hibernate_unique_key", the procedure "nextVal()" and the function "currVal()" are part of the installation procedure of the dashboard.war, which is not included in the jbpm 6.1 final package, they are missing, which causes the reinitialization of the counting in the end.

      The dashboard.war should either be part of the jbpm 6.1 final package or the creation of that MySQL thing should be moved into the console.war. Because if you install the dashboard afterwards, it also starts to count from 1.

      Attachments

        Activity

          People

            marco.rietveld Marco Rietveld (Inactive)
            tositosi Thomas Schindler (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: