[
https://issues.jboss.org/browse/JBTM-2939?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2939:
----------------------------------------
Just to add some clarification: since recovery is handling the transaction there must be a
log for it which in turn means that the prepare phase has ended and a decision has been
made to commit the transaction. Now since a resource is not allowed to forget a heuristic
decision and since the resource no longer has record of the xid it is safe to infer that
the resource has indeed successfully committed its branch (ie from the TM's point of
view this is not a heuristic).
JTS for not putting transaction to heuristic state during recovery
for XAException.XAER_NOTA
--------------------------------------------------------------------------------------------
Key: JBTM-2939
URL:
https://issues.jboss.org/browse/JBTM-2939
Project: JBoss Transaction Manager
Issue Type: Enhancement
Components: JTS
Affects Versions: 5.7.0.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
JTS moves transaction to heuristic state when participant during recovery returns
{{XAExeption.XAER_NOTA}} error code. This is a bit pointless as this particular error code
does not mean that there was some trouble with RM but that RM just already does not know
about the transaction branch. For recovery it means that the branch was
committed/rolled-back either before recovery started or in some previous recovery run
(where probably something crashed).
We can assumed the transaction was completed and ignore the {{XAER_NOTA}} (in case of
recovery). This behaviour is already present in JTA.
This came from EAP issue: JBEAP-13023 where you can find more on the reproducing.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)