[jbossts-issues] [JBoss JIRA] (JBTM-2428) JTS client side transaction context seems not being propagated to EAP server

[Tomasz Adamski (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080389#comment-13080389 ] 

Tomasz Adamski edited comment on JBTM-2428 at 6/17/15 10:44 AM:
----------------------------------------------------------------

In the attached link in TestBaseOneServer#presetClientOrb you have following config:
System.setProperty("org.omg.CORBA.ORBSingletonClass", "org.jacorb.orb.ORBSingleton");
System.setProperty("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");

This can be a problem itself and tbh I believe it shouldn't even work.
Have you changed it before running test?


was (Author: tomekadamski):
In the attached link in TestBaseOneServer#presetClientOrb you have following config:
System.setProperty("org.omg.CORBA.ORBSingletonClass", "org.jacorb.orb.ORBSingleton");
System.setProperty("org.omg.CORBA.ORBClass", "org.jacorb.orb.ORB");

Has it been changed in your test?

> JTS client side transaction context seems not being propagated to EAP server
> ----------------------------------------------------------------------------
>
>                 Key: JBTM-2428
>                 URL: https://issues.jboss.org/browse/JBTM-2428
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>    Affects Versions: 5.1.1
>            Reporter: Ondřej Chaloupka
>            Assignee: Tomasz Adamski
>
> 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 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)