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

JTS client side transaction context seems not being propagated to EAP server



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Migrated to another ITS
    • 5.1.1
    • None
    • None
    • None
    • Hide

      It's possible to use our crash recovery testsuite for checking this. I'm running JBoss EAP 7.0.0.DR3.

      It's possible to use our crash recovery testsuite for checking this. I'm running JBoss EAP 7.0.0.DR3. EAP 7.0.0.DR3: http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-7.0.0.DR3/jboss-eap-7.0.0.DR3.zip git clone https://code.engineering.redhat.com/gerrit/jbossqe-eap-tests-transactions (being at master branch) cd jbossqe-eap-tests-transactions export JBOSS_HOME=unzipped/path/of/jboss-ea-dr3 mvn clean verify -am -pl jbossts -DfailIfNoTests=false -Dtest=JMSCrashRecoveryTestCase#none -Dno.cleanup.at.teardown -Djbossts.noJTA -Dclient.side.transaction client side log could be found at jbossts/target/workdir/target/JMSCrashRecoveryTestCase_none_jts_client.log, server log is at jbossts/target/jbossas-jbossts/standalone/log/*log, surefire reports are at jbossts/target/surefire-reports/...


      It seems that transaction context is not propagated when JTS transaction is started on client.

      This was working for EAP 6.4 where iiop corba implementation was used. The testing client is based on guide [1].

      The call from client to server via IIOP [4] works fine but when I'm trying to start transaction on client side and then expecting being propagated to server, server proclaims that there is no txn in the context.

      This is how the orb is set up [2]
      This is how the transaction is started [3]
      This is how the remote call on ejb app server is done [4]

      [1] https://developer.jboss.org/wiki/TransactionPropagationWithJBoss
      [2] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l530
      [3] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/base/TestBaseOneServer.java;h=ed9b30aabe11fdb5f3290763beb167182a22a819;hb=HEAD#l511
      [4] https://code.engineering.redhat.com/gerrit/gitweb?p=jbossqe-eap-tests-transactions.git;a=blob;f=jbossts/src/test/java/org/jboss/as/test/jbossts/client/TxUtil.java;h=5dd55e22a52df6fd3845b1de5134f436f721a437;hb=HEAD#l69
      [5] [com.arjuna.ats.jts] (main) ARJUNA022251: The ORBManager is already associated with an ORB/OA.
      FINE [javax.enterprise.resource.corba._DEFAULT_.rpc.protocol] (main) "IOP01600014: (BAD_INV_ORDER) Cannot access this attribute or method at this point": org.omg.CORBA.BAD_INV_ORDER: vmcid: OMG minor code: 14 completed: No
      – or –
      FINE [javax.enterprise.resource.corba._CORBA_.rpc.presentation] (main) "IOP00110227: (BAD_PARAM) ORBDynamicStubFactoryFactoryClass property had value com.sun.corba.se.impl.presentation.rmi.bcel.StubFactoryFactoryBCELImpl, which could not be loaded by the ORB ClassLoader": org.omg.CORBA.BAD_PARAM: vmcid: SUN minor code: 227 completed: No


        Issue Links



              ochaloup@redhat.com Ondrej Chaloupka
              ochaloup@redhat.com Ondrej Chaloupka
              0 Vote for this issue
              2 Start watching this issue