September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1940) Deployment fails if @WebService#portName is missing

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1940: ----------------------------------- Summary: Deployment fails if @WebService#portName is missing Key: JBTM-1940 URL: https://issues.jboss.org/browse/JBTM-1940 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TXFramework, XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M5 Try removing portName attribute from one of the test services in the TXFramework suite. You will see that deployment fails. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1870) Create a travel-agent quickstart using compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1870?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1870: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create a travel-agent quickstart using compensations API > -------------------------------------------------------- > > Key: JBTM-1870 > URL: https://issues.jboss.org/browse/JBTM-1870 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation, TXFramework, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M5 > > > It should cover the second and third examples covered in my JUDConn presentation and the associated blog posts: > http://jbossts.blogspot.co.uk/2013/06/compensating-transactions-when-acid... > http://jbossts.blogspot.co.uk/2013/07/compensating-transactions-when-acid... -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1931) Narayana fails to compile on JDK6

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1931?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1931: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Narayana fails to compile on JDK6 > --------------------------------- > > Key: JBTM-1931 > URL: https://issues.jboss.org/browse/JBTM-1931 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, SPI > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/tom/projects/jbosstm/narayana/ArjunaJTA/spi/src/test/java/org/jboss/tm/TestSPI.java:[43,15] cannot find symbol > symbol : method lookup() > location: @interface javax.annotation.Resource > [INFO] 1 error -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1931) Narayana fails to compile on JDK6

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1931?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1931: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/450 > Narayana fails to compile on JDK6 > --------------------------------- > > Key: JBTM-1931 > URL: https://issues.jboss.org/browse/JBTM-1931 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, SPI > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/tom/projects/jbosstm/narayana/ArjunaJTA/spi/src/test/java/org/jboss/tm/TestSPI.java:[43,15] cannot find symbol > symbol : method lookup() > location: @interface javax.annotation.Resource > [INFO] 1 error -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1931) Narayana fails to compile on JDK6

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1931?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1931: ---------------------------------------- There is only one transaction manager instance in the application (arquillian test) so I will inject the TM instead of look it up. > Narayana fails to compile on JDK6 > --------------------------------- > > Key: JBTM-1931 > URL: https://issues.jboss.org/browse/JBTM-1931 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build System, SPI > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.M5 > > > [ERROR] COMPILATION ERROR : > [INFO] ------------------------------------------------------------- > [ERROR] /home/tom/projects/jbosstm/narayana/ArjunaJTA/spi/src/test/java/org/jboss/tm/TestSPI.java:[43,15] cannot find symbol > symbol : method lookup() > location: @interface javax.annotation.Resource > [INFO] 1 error -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1809) At trace logging to facilitate discovery of the transaction hierarchy

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1809?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-1809: ------------------------------------ Reopened for Alex to add missing IOR logging in the CORBA transaction interceptors. > At trace logging to facilitate discovery of the transaction hierarchy > --------------------------------------------------------------------- > > Key: JBTM-1809 > URL: https://issues.jboss.org/browse/JBTM-1809 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JTS > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.0.0.M4 > > > In a distributed JTS transaction there is insufficient information in the logs to facilitate the construction of the transaction hierarchy. > For example when a transaction propagates between 3 servers the logs on server 3 do not indicate which of the two other servers has the parent transaction. This feature is required by the [https://community.jboss.org/wiki/TransactionMonitoringAndVisualization] tool. > A possible solution is to print out the TM node identifier and the CORBA request id in the CORBA Client and Server Request Interceptors (in methods send_request and receive_request_service_contexts respectively). -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1930) Document transaction subsystem CLI

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1930?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1930: ---------------------------------------- It looks like the CLI descriptions get bundled as a resource (LocalDescriptions.properties). I'll take a copy of what we use for EAP > Document transaction subsystem CLI > ---------------------------------- > > Key: JBTM-1930 > URL: https://issues.jboss.org/browse/JBTM-1930 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.0.0.Final > > > I certainly couldn't find it by grepping our XML for the method I knew that should exist "probe". -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1665) Remove dependency on TAO

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1665?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1665: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/429 > 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: Crispin Boylan > Fix For: 5.0.0.M5 > > > 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1928) Send last x00 lines of build log when a pull fails

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1928?page=com.atlassian.jira.plugin.... ] Tom Jenkinson resolved JBTM-1928. --------------------------------- Resolution: Done Escaping all the output from a build log into JSON is not simple, feel free to reopen and work on this: https://github.com/jbosstm/narayana/pull/448 That being said, at this stage sending the build output to the contributor should be enough even if the comments on the pull don't get the stack trace too > Send last x00 lines of build log when a pull fails > -------------------------------------------------- > > Key: JBTM-1928 > URL: https://issues.jboss.org/browse/JBTM-1928 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > It would be useful for external contributors if when the pull request fails, the comment included the last few hundred lines of output so that it might provide some context to the issue. As it stands an internal engineer has to check the log -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1928) Send last x00 lines of build log when a pull fails

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1928?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1928: -------------------------------- Summary: Send last x00 lines of build log when a pull fails (was: Add last x00 lines of build log in the comment when a pull fails) > Send last x00 lines of build log when a pull fails > -------------------------------------------------- > > Key: JBTM-1928 > URL: https://issues.jboss.org/browse/JBTM-1928 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M5 > > > It would be useful for external contributors if when the pull request fails, the comment included the last few hundred lines of output so that it might provide some context to the issue. As it stands an internal engineer has to check the log -- 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

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2013