Skip to content

XA error correction#2078

Merged
tkyc merged 1 commit intomainfrom
xa-error-correction
Mar 2, 2023
Merged

XA error correction#2078
tkyc merged 1 commit intomainfrom
xa-error-correction

Conversation

@tkyc
Copy link
Copy Markdown
Contributor

@tkyc tkyc commented Feb 17, 2023

Fix for #1432

@lilgreenbird lilgreenbird added this to the 12.3.0 milestone Feb 21, 2023
e.errorCode = XAException.XAER_RMFAIL;
throw e;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this makes me wonder about other errors that we should not RMERR on. I see similar issues in Oracle as well. I'm wondering if we should check severity?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed offline, we expect the statement we call to return an XA status (including any XA errors). Any other error the driver receives, like a server-level error, it would be difficult to discern/translate those into the correct RMERR/RMFAIL status. So going with the conservative change here and only changing the specific behavior we believe should be changed from RMERR to RMFAIL. Other cases will remain the same (RMERR).

@tkyc tkyc marked this pull request as ready for review February 28, 2023 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants