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 commented on JBTM-1652: ------------------------------------- Fixed in: https://github.com/jbosstm/narayana/commit/65447525f45d40570a658c48cf5a17... > 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 -- 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, 8 months

1
0
0 / 0

[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 was: 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 -- 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, 8 months

1
0
0 / 0

[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 resolved JBTM-1652. --------------------------------- Resolution: Done > 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 -- 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, 8 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: Resolved (was: Pull Request Sent) Resolution: Done > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1623: ------------------------------------- New PR raised to reduce the memory available to Java, assuming OOM killer is firing because the OS is in danger and reducing the memory may actually help. > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1623: -------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/blacktie/pull/40, https://github.com/jbosstm/blacktie/pull/41 (was: https://github.com/jbosstm/blacktie/pull/40) > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1623) jboss-as is killed by Out of Memeory

by Paul Robinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1623?page=com.atlassian.jira.plugin.... ] Paul Robinson commented on JBTM-1623: ------------------------------------- I notice the PR was merged. Can this be resolved? > jboss-as is killed by Out of Memeory > ------------------------------------ > > Key: JBTM-1623 > URL: https://issues.jboss.org/browse/JBTM-1623 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > Attachments: consoleText.txt > > > See: http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1466 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1616) BlackTie Integration Test Framework hang

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1616?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1616: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/blacktie/pull/42 > BlackTie Integration Test Framework hang > ----------------------------------------- > > Key: JBTM-1616 > URL: https://issues.jboss.org/browse/JBTM-1616 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1465 -- 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, 8 months

1
0
0 / 0

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

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1650?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1650: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/blacktie/pull/43 > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1616) BlackTie Integration Test Framework hang

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1616?page=com.atlassian.jira.plugin.... ] Amos Feng edited comment on JBTM-1616 at 4/27/13 4:10 AM: ---------------------------------------------------------- It cased by the valgrind bad option, see following server-2121-130425020630-err.txt {noformat} valgrind: Bad option: --show-reachable=false valgrind: Invalid boolean value 'false' (should be 'yes' or 'no') valgrind: Use --help for more information or consult the user manual. {noformat} This issue happen only on blacktie-linux64 because there is "use.valgrind = true" so the fix should be use "--show-reachable=no" was (Author: zhfeng): It cased by the valgrind bad option, see following server-2121-130425020630-err.txt {noformat} valgrind: Bad option: --show-reachable=false valgrind: Invalid boolean value 'false' (should be 'yes' or 'no') valgrind: Use --help for more information or consult the user manual. {noformat} This issue happen only on blacktie-linux64 because there is "use.valgrind = true" so the fix should be use "--show-reachable=yes" > BlackTie Integration Test Framework hang > ----------------------------------------- > > Key: JBTM-1616 > URL: https://issues.jboss.org/browse/JBTM-1616 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1465 -- 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, 8 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 April 2013