[jbossts-issues] [JBoss JIRA] (JBTM-1325) Second bridged JTA transaction doesn't seem to commit if running on same server as first

[Paul Robinson (JIRA)]

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

Paul Robinson resolved JBTM-1325.
---------------------------------

    Resolution: Rejected


The problem was caused by an application bug, not a TXBridge bug.
                
> Second bridged JTA transaction doesn't seem to commit if running on same server as first
> ----------------------------------------------------------------------------------------
>
>                 Key: JBTM-1325
>                 URL: https://issues.jboss.org/browse/JBTM-1325
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: TxBridge
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M2, 4.17.3
>
>
> See here for code to reproduce (follow steps in README.md): https://github.com/paulrobinson/quickstart-1/tree/master-JBTM-1324_Create_a_TXBridge_quickstart_that_bridges_to_two_services
> Scenario:
> * 1 JTA Client
> * Invokes two WS-AT services in same JTA transaction
> * Each service bridges to a JTA transaction which update a DB
>  
> The tests succeed if the client and service one are on the first server and the second service is on a second server. The problem occurs when the client, first and second service all run on the same server.

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