Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: jBPM 3.2.2
    • Fix Version/s: SOA 4.2 CP02, jBPM 3.2.3
    • Component/s: None
    • Labels:
      None

      Description

      If in one transaction you create a new process instance and reach a join, you'll get a invalid StaleObjectStateException. The cause is that in case of oracle, hibernate will not insert the record in the database before the forced version increment in the join will be executed. That results in 0 rows updated and hence a StaleStateObjectException.

      The fix applied is that we added a flush before the forced version update in the join

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  koen.aers Koen Aers
                  Reporter:
                  tom.baeyens Tom Baeyens
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: