[jbossts-issues] [JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport

Michael Musgrove (JIRA) jira-events at lists.jboss.org
Mon Jul 22 10:21:26 EDT 2013

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

Michael Musgrove commented on JBTM-1855:

The problem is that there may be no JTS transaction. The RTS transaction could be started on any server and is most likely just a standard JTA (non JTS) transaction - this originating server is where the (RTS) coordinator for the transaction resides. When the RTS transaction propagates to another server (via XATMI) and if we want to enlist JTA resources (such as JMS connections) then these resources must be enlisted with the coordinator. But RTS does not know about JTA so the bridge enlists itself with the coordinator, starts a JTA transaction and keeps a record of which JTA resources enlist with this subsidiary JTA transaction. When the coordinator tells the bridge (acting as an RTS participant) to prepare and commit, the bridge forwards these requests to any JTA resources that have enlisted with the JTA transaction. The bridge is the only component capable of fulfilling these requirements so there is no other way.

To use the bridge we will have to make sure that the blacktie-stompconnect subsystem has a dependency on the bridge. If you track what gytis is doing with JBTM-1364 and his associated quickstart (or ping the team) then I think it will be clear what needs to be done to enable the bridge for use by the stompconnect subsystem.
> No unit tests for queue with RTS transport
> ------------------------------------------
>                 Key: JBTM-1855
>                 URL: https://issues.jboss.org/browse/JBTM-1855
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: BlackTie, REST, Testing
>            Reporter: Crispin Boylan
>            Assignee: Amos Feng
>             Fix For: 5.0.0.M4
> There are currently no tests that use RTS for C++ queue tests. You can tell this as TXN_CFG is not specific in the btconfig.xml.
> When TXN_CFG is manually added to the btconfig.xml the tests actually fail with error:
> 15:15:44,584 ERROR [jacorb.orb] (StompConnect Transport: tcp:/// Exception while converting string to object: java.lang.IllegalArgumentException: Invalid or unreadable URL/IOR: <?xml version="1.0" encoding="UTF-8" standalone="yes"?><coordinator><status>TransactionActive</status><created>1970-01-01T01:00:00.060+01:00</created><timeout>300</timeout><txnURI></txnURI><terminatorURI></terminatorURI><durableParticipantEnlistmentURI></durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI></volatileParticipantEnlistmentURI></coordinator>
>         at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:484) [jacorb-2.3.2.jbossorg-4.jar:]
>         at org.jacorb.orb.ParsedIOR.parse(ParsedIOR.java:486) [jacorb-2.3.2.jbossorg-4.jar:]
>         at org.jacorb.orb.ParsedIOR.<init>(ParsedIOR.java:225) [jacorb-2.3.2.jbossorg-4.jar:]
>         at org.jacorb.orb.ORB.string_to_object(ORB.java:1961) [jacorb-2.3.2.jbossorg-4.jar:]
>         at org.codehaus.stomp.jms.ProtocolConverter.createControlWrapper(ProtocolConverter.java:110) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
>         at org.codehaus.stomp.jms.ProtocolConverter.controlToTx(ProtocolConverter.java:98) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
>         at org.codehaus.stomp.jms.ProtocolConverter.onStompReceive(ProtocolConverter.java:310) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
>         at org.codehaus.stomp.jms.ProtocolConverter.onStompFrame(ProtocolConverter.java:172) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
>         at org.codehaus.stomp.tcp.TcpTransport.run(TcpTransport.java:103) [blacktie-stompconnect-5.0.0.M4-SNAPSHOT.jar:]
>         at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06-icedtea]

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

More information about the jbossts-issues mailing list