[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 07:17:27 EDT 2013


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

Michael Musgrove commented on JBTM-1855:
----------------------------------------

The StompConnect code that receives incoming queue requests (ProtocolConverter.java) expects the messagexid header to contain a CORBA reference to an OTS transaction. It then uses Narayana code to import the transaction into the current VM and associates the resulting transaction with the current thread. From there it relies on JMS (ie it creates an XA connection which is automatically enlisted in the transaction). This approach will not work if the incoming message refers to an RTS transaction since there is no associated JTS transaction. Instead of "importing" the OTS transaction we would need to create a local JTA transaction and use the RTS/JTA bridge to bind the two transactions together.

The code changes should be reasonably straight forward but the bridge will only be integrated in the next release (M4) by JBTM-1364  


                
> 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:///127.0.0.1:49804) 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>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d759d_51e9352b_7a3</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d759d_51e9352b_7a3/terminator</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d759d_51e9352b_7a3</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d759d_51e9352b_7a3/volatile-participant</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