[jbossts-issues] [JBoss JIRA] (JBTM-2274) Create separate assumed complete type for heuristic transactions

[Gytis Trikleris (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated JBTM-2274:
----------------------------------
    Description: 
Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move.

Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem.

  was:
Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the record after the move.

Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem.



> Create separate assumed complete type for heuristic transactions
> ----------------------------------------------------------------
>
>                 Key: JBTM-2274
>                 URL: https://issues.jboss.org/browse/JBTM-2274
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: JTS
>            Reporter: Gytis Trikleris
>            Assignee: Gytis Trikleris
>             Fix For: 4.17.24, 5.0.4
>
>
> Currently all JTS transaction records are moved to assumed complete store after 3 recovery tries. This is not good if the transaction has a heuristic outcome. It leads to the heuristic participant being rolled back, because recovery coordinator cannot see the log record after the move.
> Creating separate locations for such heuristic transactions and checking their status during replay_completion would solve the problem.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)