May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1662) idlj-maven-plugin need to be updated for missing files

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1662?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1662: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/288 > idlj-maven-plugin need to be updated for missing files > ------------------------------------------------------ > > Key: JBTM-1662 > URL: https://issues.jboss.org/browse/JBTM-1662 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > During EAP6 productization process, orb.idl and CosTransactions.idl need to be copied manually into 'idlj' component. The reason could be the idlj-maven-plugin version used is 1.0.0. > As Paul addressed, after upgrade the version to org.codehaus.mojo-idlj-maven-plugin-1.2.1_redhat_1-1, the problem gone. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1663) JBossTS - EAP6 productization issue tracker

by Weinan Li (JIRA)

[ https://issues.jboss.org/browse/JBTM-1663?page=com.atlassian.jira.plugin.... ] Weinan Li updated JBTM-1663: ---------------------------- Description: This is the tracker for all the issues I've found during EAP6 productization process. (was: During EAP6 productization process, orb.idl and CosTransactions.idl need to be copied manually into 'idlj' component. The reason could be the idlj-maven-plugin version used is 1.0.0. As Paul addressed, after upgrade the version to org.codehaus.mojo-idlj-maven-plugin-1.2.1_redhat_1-1, the problem gone. ) > JBossTS - EAP6 productization issue tracker > ------------------------------------------- > > Key: JBTM-1663 > URL: https://issues.jboss.org/browse/JBTM-1663 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Affects Versions: 4.17.4 > Reporter: Weinan Li > Assignee: Tom Jenkinson > > This is the tracker for all the issues I've found during EAP6 productization process. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1662) idlj-maven-plugin need to be updated for missing files

by Weinan Li (JIRA)

Weinan Li created JBTM-1662: ------------------------------- Summary: idlj-maven-plugin need to be updated for missing files Key: JBTM-1662 URL: https://issues.jboss.org/browse/JBTM-1662 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Tom Jenkinson During EAP6 productization process, orb.idl and CosTransactions.idl need to be copied manually into 'idlj' component. The reason could be the idlj-maven-plugin version used is 1.0.0. As Paul addressed, after upgrade the version to org.codehaus.mojo-idlj-maven-plugin-1.2.1_redhat_1-1, the problem gone. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1663) JBossTS - EAP6 productization issue tracker

by Weinan Li (JIRA)

Weinan Li created JBTM-1663: ------------------------------- Summary: JBossTS - EAP6 productization issue tracker Key: JBTM-1663 URL: https://issues.jboss.org/browse/JBTM-1663 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Build System Affects Versions: 4.17.4 Reporter: Weinan Li Assignee: Tom Jenkinson During EAP6 productization process, orb.idl and CosTransactions.idl need to be copied manually into 'idlj' component. The reason could be the idlj-maven-plugin version used is 1.0.0. As Paul addressed, after upgrade the version to org.codehaus.mojo-idlj-maven-plugin-1.2.1_redhat_1-1, the problem gone. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1650) SIGPIPE as xatmi test tearDown() is calling tpdiscon()

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1650: ------------------------------------- This shows the effect the proposed fix on Windows: http://172.17.131.2/job/btny-pulls-blacktie-windows2008/155/console I am trying a commit to #ifndef WIN32 to revert the behaviour on windows, however I do not know why the change is only required on linux 64. Also the change does appear to work on linux 32 (even though it wasn't failing on linux 32). > SIGPIPE as xatmi test tearDown() is calling tpdiscon() > ------------------------------------------------------ > > Key: JBTM-1650 > URL: https://issues.jboss.org/browse/JBTM-1650 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > ==7024== > ==7024== Process terminating with default action of signal 13 (SIGPIPE) > ==7024== at 0x363040E5CD: ??? (in /lib64/libpthread-2.14.90.so) > ==7024== by 0x7044D56: apr_socket_send (in /usr/lib64/libapr-1.so.0.4.6) > ==7024== by 0x76FF688: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:287) > ==7024== by 0x76FF878: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:325) > ==7024== by 0x76FA50F: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:519) > ==7024== by 0x92B629D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==7024== by 0x92B66B8: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:182) > ==7024== by 0x92C1051: tpdiscon (XATMIc.cxx:1219) > ==7024== by 0x44416D: TestTPRecv::tearDown() (TestTPRecv.cxx:63) > ==7024== by 0x445584: CppUnit::TestCaller<TestTPRecv>::tearDown() (TestCaller.h:182) > ==7024== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==7024== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==7024== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==7024== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==7024== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==7024== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==7024== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==7024== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==7024== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==7024== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==7024== by 0x4E2043: main (TestRunner.cxx:27) -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1645: -------------------------------- Priority: Minor (was: Critical) > Allow pull requests to configure some parameters in scripts/hudson/narayana.sh > ------------------------------------------------------------------------------ > > Key: JBTM-1645 > URL: https://issues.jboss.org/browse/JBTM-1645 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the pull description has something like this: > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests] > We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1645) Allow pull requests to configure some parameters in scripts/hudson/narayana.sh

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1645: -------------------------------- Priority: Major (was: Minor) > Allow pull requests to configure some parameters in scripts/hudson/narayana.sh > ------------------------------------------------------------------------------ > > Key: JBTM-1645 > URL: https://issues.jboss.org/browse/JBTM-1645 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If the pull description has something like this: > export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1 XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests] > We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might need to white list users we apply this to. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1468) Support pure-JTA client and server for WS-AT and REST-AT

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1468?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1468: -------------------------------- Priority: Minor (was: Major) > Support pure-JTA client and server for WS-AT and REST-AT > -------------------------------------------------------- > > Key: JBTM-1468 > URL: https://issues.jboss.org/browse/JBTM-1468 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: REST, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > This allows the Client and server application to just use the JTA APIs, whilst having the distribution done over WS-AT or REST-AT. > To do this we need to: > # Remove @Transactional annotation. We then need to use some other mechanism to support the (optional) WS-AT participants that want to use annotations. > # Client side JTA->REST-AT bridge. Needs implementing. > # Server side REST-AT->JTA bridge. Needs integrating into code base. > # Update the TXBridge quickstarts to use this and move them out. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1472) Initial work on Compensations API

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1472?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1472: -------------------------------- Summary: Initial work on Compensations API (was: Initial work on JTA for Compensations) > Initial work on Compensations API > --------------------------------- > > Key: JBTM-1472 > URL: https://issues.jboss.org/browse/JBTM-1472 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core, XTS > Reporter: Paul Robinson > Assignee: Paul Robinson > Fix For: 5.0.0.M3 > > Original Estimate: 2 weeks > Time Spent: 1 week, 6 hours > Remaining Estimate: 1 week, 4 days, 2 hours > > We essentially provide a JTA-like implementation for using compensations. We would support distribution over Web services and REST via WS-BA and REST-JDI. This is similar in how we do distributed ACID transactions today; the application is developed against the JTA, but through configuration we enable distributed transactions over a particular transport (remoting, IIOP, WS). > It would be good to have some subset of functionality that worked on a raw VM (i.e. no appserver). This would hopefully broaden the market. > This first piece of work is to do some initial research and support an API with potentially a subset of features of the final API. > Tasks: > # Investigate existing WS-BA APIs > ## Try code examples if possible > # Produce an initial list of features that should be covered by the API > # Create a simple implementation backed by WS-BA. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1660) Implement JTA 1.2 @Transactional feature

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1660?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1660: -------------------------------- Parent: JBTM-1497 Issue Type: Sub-task (was: Feature Request) > Implement JTA 1.2 @Transactional feature > ---------------------------------------- > > Key: JBTM-1660 > URL: https://issues.jboss.org/browse/JBTM-1660 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JTA > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > Implement Section "3.7 Transactional Annotation" of the JTA 1.2 specification. -- 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

12 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2013