[jbossts-issues] [JBoss JIRA] (JBTM-2733) Adding section about inflow transactions and EIS interaction

[Ondra Chaloupka (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291095#comment-13291095 ] 

Ondra Chaloupka commented on JBTM-2733:
---------------------------------------

Hi [~tomjenkinson], I  was wondering on your comment https://issues.jboss.org/browse/JBTM-2733?focusedCommentId=13284121#comment-13284121 and now I found some time to go through the XA spec for it. I wasn't able to find reason behind why the recover sequence should be {{xa_recover(START), xa_commit/rb, xa_recover(END)}} and can't be e.g. like {{xa_recover(START|END), xa_commit/rb}}. Would you be so kind and elaborate a bit on this? Or can you point me to spec/article where I got information how this is expected to be used? It's quite possible that I just haven't read/searched properly.

I'm just curious.

Thanks in advance.

> Adding section about inflow transactions and EIS interaction
> ------------------------------------------------------------
>
>                 Key: JBTM-2733
>                 URL: https://issues.jboss.org/browse/JBTM-2733
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>          Components: Documentation
>    Affects Versions: 5.3.4.Final
>            Reporter: Ondra Chaloupka
>            Assignee: Tom Jenkinson
>
> I would like ask for enhancing Narayana documentation for section where information about inflow transactions and interaction with EIS would be part of.
> This ask for the addition came from discussion about behaviour of inflow transaction on jbossts mailing list. Particularly information how EIS and TM is expected to interoperate during recovery process. E.g. how EIS is expected to finish transaction when TM jvm crash occurs or how EIS is expected to finish transaction when participant of txn involved under management of TM (TM is manager of subordinate transaction) and such participant independently decides to rollback (after prepare is confirmed) which causes heuristic exception being thrown to EIS RAR and transaction is put to heuristic state.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)