April 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1652) Move from JBoss-AS to Wildfly

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1652?page=com.atlassian.jira.plugin.... ] Paul Robinson updated JBTM-1652: -------------------------------- Description: h2. Changed: git repo name build/target/jboss-as-8.0.0.Alpha1 -> build/target/wildfly-8.0.0.Alpha1 h2. Not yet changed: Maven artefact names > Move from JBoss-AS to Wildfly > ----------------------------- > > Key: JBTM-1652 > URL: https://issues.jboss.org/browse/JBTM-1652 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Paul Robinson > Priority: Critical > Fix For: 5.0.0.M3 > > > h2. Changed: > git repo name > build/target/jboss-as-8.0.0.Alpha1 -> build/target/wildfly-8.0.0.Alpha1 > h2. Not yet changed: > Maven artefact names -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1652) Move from JBoss-AS to Wildfly

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1652: ----------------------------------- Summary: Move from JBoss-AS to Wildfly Key: JBTM-1652 URL: https://issues.jboss.org/browse/JBTM-1652 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Paul Robinson Assignee: Paul Robinson Priority: Critical Fix For: 5.0.0.M3 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1646) IndirectTXManagementTest failed. rest-tx.realm is already registered

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1646?page=com.atlassian.jira.plugin.... ] Michael Musgrove resolved JBTM-1646. ------------------------------------ Resolution: Done The quickstart assumes that the restat war is already deployed but the hudson config was copying the file to the wrong location > IndirectTXManagementTest failed. rest-tx.realm is already registered > -------------------------------------------------------------------- > > Key: JBTM-1646 > URL: https://issues.jboss.org/browse/JBTM-1646 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Demonstrator, REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/btny-pulls-quickstarts/227 > http://172.17.131.2/job/btny-pulls-quickstarts/226 > http://172.17.131.2/job/btny-pulls-quickstarts/225 -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1651) Node name length protection is incorrectly defined

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1651?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1651: -------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/280, https://github.com/jbosstm/narayana/pull/281 (was: https://github.com/jbosstm/narayana/pull/280) > Node name length protection is incorrectly defined > -------------------------------------------------- > > Key: JBTM-1651 > URL: https://issues.jboss.org/browse/JBTM-1651 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.5, 5.0.0.M3 > > > The value is set to 64, in reality this must be less that 28 to fit in the bqual with the EIS name and Uid. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1651) Node name length protection is incorrectly defined

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1651?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1651: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/280 > Node name length protection is incorrectly defined > -------------------------------------------------- > > Key: JBTM-1651 > URL: https://issues.jboss.org/browse/JBTM-1651 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 4.17.5, 5.0.0.M3 > > > The value is set to 64, in reality this must be less that 28 to fit in the bqual with the EIS name and Uid. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1651) Node name length protection is incorrectly defined

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1651: ----------------------------------- Summary: Node name length protection is incorrectly defined Key: JBTM-1651 URL: https://issues.jboss.org/browse/JBTM-1651 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Priority: Critical Fix For: 4.17.5, 5.0.0.M3 The value is set to 64, in reality this must be less that 28 to fit in the bqual with the EIS name and Uid. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-919) Convert tests to work on Windows

by Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-919?page=com.atlassian.jira.plugin.s... ] Ondřej Chaloupka reassigned JBTM-919: ------------------------------------- Assignee: Jan Martiska (was: Ondřej Chaloupka) > Convert tests to work on Windows > -------------------------------- > > Key: JBTM-919 > URL: https://issues.jboss.org/browse/JBTM-919 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Tom Jenkinson > Assignee: Jan Martiska > Priority: Minor > > Some of the tests cannot be ran on Windows which reduces our scope for testing and also leaves some hudson nodes idle. -- 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, 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 commented on JBTM-1645: ------------------------------------- Yeah, I guess there will be situations like that. Maybe we just have one skip command per sub-job: !MAIN !XTS !QA_JTA !QA_JTS_JACORB !QA_JTS_JDKORB Less magic then. > 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: Critical > 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

11 years, 5 months

1
0
0 / 0

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

by Amos Feng (JIRA)

Amos Feng created JBTM-1650: ------------------------------- Summary: 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

11 years, 5 months

1
0
0 / 0

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1645: ------------------------------------- How about if the pull just changes a JacORB qa test? Or just an XTS test, that would be rationale to skip MAIN wouldn't it? Agreed on the white listing, we just need to be vigilant :) > 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: Critical > 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

11 years, 5 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 April 2013