Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2853

Transaction bridging for WS not working because of switch to new wfly transaction client

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 5.5.2.Final
    • Fix Version/s: 5.5.4.Final
    • Component/s: TxBridge
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Narayana txbridge testcase

      mvn clean install -Parq -Dtest=InboundBasicTests
      
      Show
      Narayana txbridge testcase mvn clean install -Parq -Dtest=InboundBasicTests

      Description

      Transaction bridging (WS transaction <-> global container transaction) does not work currently as container is impacted by switch from transaction spi (https://github.com/jbosstm/jboss-transaction-spi) to wildfly transaction client (https://github.com/wildfly/wildfly-transaction-client).

      The cause code change could be checked here
      https://github.com/wildfly/wildfly/commit/5eb816e0b58da3e99bfee81715ba27b65e8c75fc

      Narayana needs to be enhanced to use the new transaction client to import transaction and bridge the ws to container transaction that way. The similar thing will probably need to be done for opposite side.
      Container integration code in jboss container needs to be changed in way to provide the transaction context to Narayana.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  ochaloup Ondrej Chaloupka
                  Reporter:
                  ochaloup Ondrej Chaloupka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: