Uploaded image for project: 'Corda'
  1. CORDA-1790

Backport to 3.2 the fix that prevents the database to end up in an inconsistent state

    Details

    • Type: Bug
    • Status: Done (View workflow)
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Corda 3.2, Corda 3.3
    • Component/s: None
    • Labels:
      None
    • Severity:
      Medium
    • Target Version/s:
    • Feature Team:
      Corda Core
    • Sprint:

      Description

      In version 3.0 of OS, the database will end up in an inconsistent state if an exception is thrown in HibernateObserver.persistStatesWithSchema

      To replicate:

      • throw exception in HibernateObserver.persistStatesWithSchema
      • deploy traderdemo
      • runBank
      • check the database in Bank of Corda. There should be a transaction entry in the node_transactions and vault_states, but no entry in the Cash or Commercial Paper tables.

      On master, same steps, and all tables will be empty ( so the transaction rolled back), which is the correct behaviour.

      It is not clear what change actually fixed the issue.

      Will fix: https://stackoverflow.com/questions/50931075/initiator-unable-to-commit-states-to-vault-linear-states-after-notary-signed

        Attachments

          Activity

            People

            • Assignee:
              Tudor.Malene Tudor Malene
              Reporter:
              Tudor.Malene Tudor Malene
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: