This repository was archived by the owner on Sep 18, 2025. It is now read-only.
JBTM-2819 Clarify the semantics of clearing a heuristic #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Started testing this pull request: http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-documentation/6/ |
mmusgrov
commented
Dec 16, 2016
| <literal>HEURISTIC</literal> | ||
| , the clearHeuristic operation changes the state to | ||
| If the transaction participant's status is | ||
| <literal>HEURISTIC</literal> or |
There was a problem hiding this comment.
When does a participant end up in this unknown heuristic state (ie it should be one of mixed, hazard, rollback or commit)?
There was a problem hiding this comment.
I will investigate in the next release.
|
@tomjenkinson I do not seem to be able to mark this as ready for review on my phone but will be back at my desk in 30 minutes or so. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://issues.jboss.org/browse/JBTM-2821