[JBoss JIRA] (JBTM-1469) Move TXBridge quickstart into JDF
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1469?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson updated JBTM-1469:
--------------------------------
Component/s: Demonstrator
> Move TXBridge quickstart into JDF
> ---------------------------------
>
> Key: JBTM-1469
> URL: https://issues.jboss.org/browse/JBTM-1469
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Demonstrator, TxBridge, XTS
> Reporter: Paul Robinson
> Assignee: Paul Robinson
> Priority: Minor
> Fix For: 5.0.0.Final
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
> TXBridge is now supported, so we can move one or more of the quickstarts across to JDF. We should first run this by Pete and get a JDF Jira created, then link this one through.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months
[JBoss JIRA] (JBTM-1786) Change to TMFAIL for an ABORT on a non-prepared TX
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1786?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson resolved JBTM-1786.
---------------------------------
Resolution: Done
Hi John,
Once your PR is merged we usually mark these as resolved - I will do it for you this time :)
Thanks for the contribution!
Tom
> Change to TMFAIL for an ABORT on a non-prepared TX
> --------------------------------------------------
>
> Key: JBTM-1786
> URL: https://issues.jboss.org/browse/JBTM-1786
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA, JTS
> Affects Versions: 4.16.4
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
>
> An ABORT on a non-prepared TX should be calling end with TMFAIL.
> It's more efficient in that the RM can return an RB* code immediately and short circuit the rollback internally if it likes. More importantly though the RM is less likely to object that it's still running tx activity on another thread and the concurrent TMSUCCESS therefore makes no sense to it.
> Also the XAResourceRecord.topLevelAbort code should immediately continue on to calling rollback on the resource despite the failed end().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 9 months