Tag onCommit/onRollback Changes with unique identifiers to log in case they throw when later run

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If some Change fails in the RecoveryUnit::commitRegisteredChanges() or abortRegisteredChanges functions, we have the error message, but we have no trace of where the code for the Change is: it won't be in a stack trace. It would help diagnose issues more quickly if we could immediately identify where in the code to find the Change definition.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Dianna Hohensee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: