[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
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_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</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
10 years, 10 months
[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1854:
-----------------------------------
Attachment: (was: CurrentTests01_Test036.tar)
> Hornetq failures in CI test suite
> ---------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz
>
>
> There were quite a few failures so I am simply listing them here and referencing the job for further investigation:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
--
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
10 years, 10 months
[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1854:
-----------------------------------
Attachment: CurrentTests01_Test036.tar.gz
> Hornetq failures in CI test suite
> ---------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz
>
>
> There were quite a few failures so I am simply listing them here and referencing the job for further investigation:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
--
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
10 years, 10 months
[JBoss JIRA] (JBTM-1854) Hornetq failures in CI test suite
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-1854:
-----------------------------------
Attachment: CurrentTests01_Test036.tar
idlj-failures.tar.gz
> Hornetq failures in CI test suite
> ---------------------------------
>
> Key: JBTM-1854
> URL: https://issues.jboss.org/browse/JBTM-1854
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Testing
> Affects Versions: 5.0.0.M3
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.M4
>
> Attachments: CurrentTests01_Test036.tar, idlj-failures.tar.gz
>
>
> There were quite a few failures so I am simply listing them here and referencing the job for further investigation:
> CurrentTests01_Test036
> jtsremote JTSRemote_ImplicitPropagationTest
> crashrecovery02_2 CrashRecovery02_2 - all of them
> crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10
> crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them)
--
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
10 years, 10 months
[JBoss JIRA] (JBTM-1749) Failure building Javadoc when JAVA_HOME is empty
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1749?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1749:
-------------------------------------
This looks to be a known issue in older versions of javadoc: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6442982
As mark has already documented the work around, I think we should resolve this as "Done". I can confirm on linux at least setting JAVA_HOME to a JDK 7 installation _does_ work. Maybe a Mac user can confirm JAVA_HOME to a JDK7 installation works or we can just mark this resolved?
> Failure building Javadoc when JAVA_HOME is empty
> ------------------------------------------------
>
> Key: JBTM-1749
> URL: https://issues.jboss.org/browse/JBTM-1749
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build System
> Environment: See discussion
> Reporter: Paul Robinson
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 5.0.0.M4
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> To reproduce:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.5/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> It also happens if you use the maven version in tools/maven (also version 3.0.5).
> This doesn't fail:
> # export JAVA_HOME=
> # /opt/apache-maven-3.0.3/bin/mvn clean install -DskipTests -f ./ArjunaJTA/narayana-jta/pom.xml
> Currently only seen this on a Mac. Would be good if a linux user could try to reproduce.
> Maven 3.0.5 is the latest release. I've not found a known issue for this, but it is hard to search for.
--
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
10 years, 10 months
[JBoss JIRA] (JBTM-1665) Remove dependency on TAO
by Crispin Boylan (JIRA)
[ https://issues.jboss.org/browse/JBTM-1665?page=com.atlassian.jira.plugin.... ]
Crispin Boylan commented on JBTM-1665:
--------------------------------------
I am working on this and it is passing most of the tests now, except for the queue based ones which fail when using RTS (which will be mandatory as of this change), due to JBTM-1855.
> Remove dependency on TAO
> ------------------------
>
> Key: JBTM-1665
> URL: https://issues.jboss.org/browse/JBTM-1665
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Fix For: 5.0.0.Final
>
>
> Part of the purpose of adding the socket server was to reduce the dependency on TAO, e.g.:
> ==6038== 20 bytes in 1 blocks are still reachable in loss record 7 of 54
> ==6038== at 0x4026011: calloc (vg_replace_malloc.c:593)
> ==6038== by 0x55C90A5: _dlerror_run (in /lib/libdl-2.12.so)
> ==6038== by 0x55C8B70: dlopen@(a)GLIBC_2.1 (in /lib/libdl-2.12.so)
> ==6038== by 0x40E2875: ACE_DLL_Handle::open(char const*, int, void*) (OS_NS_dlfcn.inl:124)
> ==6038== by 0x40E2D2B: ACE_DLL_Manager::open_dll(char const*, int, void*) (DLL_Manager.cpp:575)
> ==6038== by 0x40A3943: ACE_DLL::open_i(char const*, int, bool, void*) (DLL.cpp:167)
> ==6038== by 0x40A3AAA: ACE_DLL::open(char const*, int, bool) (DLL.cpp:127)
> ==6038== by 0x40A4C0A: ACE_Location_Node::open_dll(int&) (Parse_Node.cpp:479)
> ==6038== by 0x40A4D4B: ACE_Function_Node::symbol(ACE_Service_Gestalt*, int&, void (**)(void*)) (Parse_Node.cpp:657)
> ==6038== by 0x40A5627: ACE_Service_Type_Factory::make_service_type(ACE_Service_Gestalt*) const (Parse_Node.cpp:880)
> ==6038== by 0x40ACEA6: ACE_Service_Gestalt::initialize(ACE_Service_Type_Factory const*, char const*) (Service_Gestalt.cpp:552)
> ==6038== by 0x40A5555: ACE_Dynamic_Node::apply(ACE_Service_Gestalt*, int&) (Parse_Node.cpp:326)
> ==6038== by 0x40B3302: ace_yyparse(void*) (Svc_Conf_y.cpp:1440)
> ==6038== by 0x40AA5C7: ACE_Service_Gestalt::process_directives_i(ACE_Svc_Conf_Param*) (Service_Gestalt.cpp:800)
> ==6038== by 0x40AD407: ACE_Service_Gestalt::process_directive(char const*) (Service_Gestalt.cpp:940)
> ==6038== by 0x4287A65: TAO::ORB::open_global_services(int, char**) (Service_Config.inl:154)
> ==6038== by 0x4247EB3: CORBA::ORB_init(int&, char**, char const*) (ORB.cpp:1254)
> ==6038== by 0x49172F6: initOrb(char*) (OrbManagement.cxx:73)
> ==6038== by 0x4AB97C4: atmibroker::tx::OTSTxManager::OTSTxManager(char*) (OTSTxManager.cxx:39)
> ==6038== by 0x4ABA054: atmibroker::tx::OTSTxManager::create(char*) (OTSTxManager.cxx:57)
> ==6038== by 0x4AB0BDC: atmibroker::tx::TxManager::get_instance() (TxManager.cxx:63)
> ==6038== by 0x4AE7D06: txManager_open() (TxManagerAvoid.cxx:23)
> ==6038== by 0x4AD74D4: tx_open (TxAvoid.cxx:53)
> ==6038== by 0x804FF8D: TestXAStompConnection::test() (TestXAStompConnection.cxx:79)
> ==6038== by 0x805945B: CppUnit::TestCaller<TestXAStompConnection>::runTest() (TestCaller.h:166)
> ==6038== by 0xA5DC76: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32)
> ==6038== by 0xA4F53D: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15)
> ==6038== by 0xA59812: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20)
> ==6038== by 0xA59544: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77)
> ==6038== by 0xA65EF0: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178)
> ==6038== by 0xA5D97C: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:92)
> ==6038== by 0xA5E2DE: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==6038== by 0xA5E219: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==6038== by 0xA5E2DE: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64)
> ==6038== by 0xA5E219: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23)
> ==6038== by 0xA6850F: CppUnit::TestRunner::WrappingSuite::run(CppUnit::TestResult*) (TestRunner.cpp:47)
> ==6038== by 0xA65C89: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145)
> ==6038== by 0xA6834F: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96)
> ==6038== by 0xA6BA7A: CppUnit::TextTestRunner::run(CppUnit::TestResult&, std::string const&) (TextTestRunner.cpp:140)
> ==6038== by 0xA6BAF4: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64)
--
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
10 years, 10 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-1855:
---------------------------------
Tom, the blacktie-stompconnect is moving into wildfly-blacktie subsystem now. I will take a look at this issue when JBTM-1568 and JBTM-1847 resolved.
> 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_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</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
10 years, 10 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Crispin Boylan (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Crispin Boylan commented on JBTM-1855:
--------------------------------------
Amos, I also have a feeling that the same problem will occur when using a transaction between a C xatmi call using RTS and a java one, because the same code exists for handling the messagecontrol parameter as it does for handling the messagexid in stompconnect.
> 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_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</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
10 years, 10 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Crispin Boylan (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Crispin Boylan updated JBTM-1855:
---------------------------------
Description:
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_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</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]
was:
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.
> 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_107d7...</txnURI><terminatorURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</terminatorURI><durableParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</durableParticipantEnlistmentURI><volatileParticipantEnlistmentURI>http://127.0.0.1:8080/rest-tx/tx/transaction-manager/0_ffff7f000001_107d7...</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
10 years, 10 months
[JBoss JIRA] (JBTM-1855) No unit tests for queue with RTS transport
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1855?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1855:
-------------------------------------
Hi Amos,as we are looking to move to using RTS rather than JTS it is ok to convert the test suite to not use JTS and just use RTS.
> 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.
--
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
10 years, 10 months