Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-3247

Failed LRA records are reported but they not kept

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Done
    • Icon: Blocker Blocker
    • 5.10.5.Final
    • 5.10.3.Final
    • LRA
    • None

      When an LRA is closed/cancelled and some participants will never be able to complete/compensate then they are placed on the [BasicAction] failedList. The MP-LRA spec only requires that such failures are logged. The narayana implementation does indeed log the failure (using a log WARNING statement) but then removes the transaction record from the object store.

      It would be preferable to leave failed LRA's in the store and allow them to be queried and deleted using the REST coordinator (like we do for recovering LRA's).

            [JBTM-3247] Failed LRA records are reported but they not kept

            Michael Musgrove added a comment -

            The fix should also incorporate JBTM-3141 which I will close.

            Michael Musgrove added a comment - The fix should also incorporate JBTM-3141 which I will close.

            Michael Musgrove added a comment -

            I raised this as blocker since transaction failures need to be visible to the end user.

            Michael Musgrove added a comment - I raised this as blocker since transaction failures need to be visible to the end user.

            Tom Jenkinson added a comment -

            There is an area where they are not logged: https://github.com/jbosstm/narayana/pull/1559/files/b8f54959b9a418bcb8ca41e8bb518b6e61dc0180#r376714289

            Tom Jenkinson added a comment - There is an area where they are not logged: https://github.com/jbosstm/narayana/pull/1559/files/b8f54959b9a418bcb8ca41e8bb518b6e61dc0180#r376714289

              rhn-engineering-mmusgrov Michael Musgrove
              rhn-engineering-mmusgrov Michael Musgrove
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: