[jbossts-issues] [JBoss JIRA] (JBTM-1099) WS-BA to 2xJTA bridge

[Paul Robinson (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel\#worklog-{worklog.getId()} ]

Paul Robinson logged work on JBTM-1099:
---------------------------------------

                Author: Paul Robinson
            Created on: 25/Jan/13 10:06 AM
            Start Date: 25/Jan/13 10:06 AM
    Worklog Time Spent: 3 hours 

Issue Time Tracking
-------------------

    Remaining Estimate: 4 days, 5 hours  (was: 1 week)
            Time Spent: 3 hours
            Worklog Id:     (was: 12428506)


> WS-BA to 2xJTA bridge
> ---------------------
>
>                 Key: JBTM-1099
>                 URL: https://issues.jboss.org/browse/JBTM-1099
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: TXFramework
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>              Labels: assign
>             Fix For: 5.0.0.M2
>
>   Original Estimate: 1 week
>          Time Spent: 3 hours
>  Remaining Estimate: 4 days, 5 hours
>
> It is likely that a WS using WS-BA will use a JTA transaction in the service, Compensate and Close methods. The problem is that failure windows exist in this scenario. For example, when a JTA transaction is committed in the service method, a failure before confirmCompleted(true) is invoked will result in this commit not being compensated. 
> There may be other windows in Compensate and Close. This needs investigating.
> The WS-BA to JTA bridge would ensure that the transaction is not committed until confirmCompleted(true) is invoked. It should do something similar for Compensate and Close.
> This would need extensive testing, including crash recovery. The WS-AT JTA bridge (TXBridge) can be used as an example, as I believe it will have a lot in common.

--
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