May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1650) SIGPIPE as test_tprecv_sendonly 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: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/blacktie/pull/43, https://github.com/jbosstm/blacktie/pull/47 (was: https://github.com/jbosstm/blacktie/pull/43) > SIGPIPE as test_tprecv_sendonly 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 > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1597) xatmi job crashed

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1597?page=com.atlassian.jira.plugin.... ] Amos Feng resolved JBTM-1597. ----------------------------- Resolution: Duplicate Issue duplicate of JBTM-1650 > xatmi job crashed > ----------------- > > Key: JBTM-1597 > URL: https://issues.jboss.org/browse/JBTM-1597 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1462/console > It happens at the following > {code} > TestTPRecv::tearDown { > if(cd !=-1) { > ::tpdiscon(cd); > } > } > {code} > it looks like a memory issue in HybridSocketEndpointQueue::_send() and I think the test might crash with SIGSEV. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1683) btadmin tests on windows failed with "Could not start the server"

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1683?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1683: -------------------------------- Priority: Major (was: Critical) > btadmin tests on windows failed with "Could not start the server" > ----------------------------------------------------------------- > > Key: JBTM-1683 > URL: https://issues.jboss.org/browse/JBTM-1683 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M3 > > > http://172.17.131.2/job/blacktie-windows2008-taconic/272 > {code} > Failed tests: > testResumeResumeDomain(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Command was not successful > testResumeDomainWithArg(org.jboss.narayana.blacktie.btadmin.ResumeDomainTest): Could not start the server > testShutdownWithId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithoutId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testShutdownWithInvalidId(org.jboss.narayana.blacktie.btadmin.ShutdownTest): Could not start the server > testStartup(org.jboss.narayana.blacktie.btadmin.StartupTest): Command was unsuccessful > testUnadvertiseWithoutServer(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseNoArgs(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testAdvertiseNotAdvertised(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertise(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > testUnadvertiseWithoutService(org.jboss.narayana.blacktie.btadmin.UnadvertiseTest): Could not start the server > {code} -- 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, 4 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?focusedWorklogId=12429123&page=... ] Paul Robinson logged work on JBTM-1660: --------------------------------------- Author: Paul Robinson Created on: 08/May/13 3:05 PM Start Date: 08/May/13 3:04 PM Worklog Time Spent: 3 hours Issue Time Tracking ------------------- Remaining Estimate: 2 days, 5 hours (was: 3 days) Time Spent: 1 day, 3 hours (was: 1 day) Worklog Id: (was: 12429123) > 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 > Time Spent: 1 day, 3 hours > Remaining Estimate: 2 days, 5 hours > > 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1525: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove version numbers from all but parent pom > ---------------------------------------------- > > Key: JBTM-1525 > URL: https://issues.jboss.org/browse/JBTM-1525 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > We have a lot of version numbers scattered throughout our poms. Most of which should be in the root pom. This task is to hunt them all down and move the versions into the root. > I think this finds them: > {code} > grep -r "<version>" **/*/pom.xml > {code} > Not sure if it gets them all. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1611) Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09, 10, 12 with jacorb and HornetQ object store enabled

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-1611: ---------------------------------------- It works on 4.17.3.Final It fails on 4.17.4.Final I am busy going through the diffs to see what broke it! > Failing qa testcase org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09,10,12 with jacorb and HornetQ object store enabled > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-1611 > URL: https://issues.jboss.org/browse/JBTM-1611 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Testing > Affects Versions: 4.17.3 > Reporter: Ondřej Chaloupka > Assignee: Michael Musgrove > Fix For: 4.17.5, 5.0.0.M3 > > Attachments: 0001-JBTM-1611-Make-recovery-passes-configurable.patch > > > During testing EAP 6.1.0.ER3 I'm hitting problem on QA tests of narayana project for branch 4.17 when running qa tests with jacorb and hornetq object store (happening for NIO and AIO). > Tests which are failing: > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery09 > - CrashRecovery09_Test01 > - CrashRecovery09_Test03 > - CrashRecovery09_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery10 > - CrashRecovery10_Test01 > - CrashRecovery10_Test03 > - CrashRecovery10_Test05 > org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery12 > - CrashRecovery12_Test03 > - CrashRecovery12_Test06 > Detailed log could be found in job: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-61-jbossts-qa-te... > I was trying to get more info on the test CrashRecovery09 but I can say just that the value honlder has value 0 instead of 1 on org.jboss.jbossts.qa.CrashRecovery09Clients.Client01a (line 84). -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1365) Deploy REST-AT support as a JBossAS subsystem and module

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-1365?focusedWorklogId=12429122&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 08/May/13 12:31 PM Start Date: 08/May/13 12:31 PM Worklog Time Spent: 1 day, 2 hours Issue Time Tracking ------------------- Remaining Estimate: 1 week, 3 days, 6 hours, 50 minutes (was: 2 weeks, 50 minutes) Time Spent: 1 week, 1 day, 1 hour, 10 minutes (was: 4 days, 7 hours, 10 minutes) Worklog Id: (was: 12429122) > Deploy REST-AT support as a JBossAS subsystem and module > -------------------------------------------------------- > > Key: JBTM-1365 > URL: https://issues.jboss.org/browse/JBTM-1365 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: REST > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M3 > > Original Estimate: 3 weeks > Time Spent: 1 week, 1 day, 1 hour, 10 minutes > Remaining Estimate: 1 week, 3 days, 6 hours, 50 minutes > > Currently a user of REST-AT needs to deploy the coordinator and also create a new module for the REST-AT client support. It would be a lot easier for developers if this was already deployed as part of AS7. > I think the way to do this is to create a sub-system for the coordinator (like what we do for the XTS coordinator) and a module for the REST-AT libraries (again, similar to XTS). > The subsystem would need to: > * Bootstrap the coordinator. Currently bootstrapping occurs when the coordinator war is deployed. As there will be no war, the subsystem needs to take care of this bootstrapping. > * Deploy the coordinator endpoint. > The module would need to contain the REST-AT coordinator code and the client libraries. > h3. Open Issues > Need to check with the AS team to see if we add a new Subsystem or make do with an existing one. We can't start this work until this is resolved. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1618) Git pull requests: retest this please!

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1618?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1618: -------------------------------- Fix Version/s: 5.0.0.Final (was: 5.0.0.M3) > Git pull requests: retest this please! > -------------------------------------- > > Key: JBTM-1618 > URL: https://issues.jboss.org/browse/JBTM-1618 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Trivial > Fix For: 5.0.0.Final > > > If someone comments on a pull requesting a retest it would be nice that a job got scheduled. > I don't really know how easy it is to do that, maybe the build bot needs to respond to emails? -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-1525: ----------------------------------- Assignee: Tom Jenkinson (was: Amos Feng) > Remove version numbers from all but parent pom > ---------------------------------------------- > > Key: JBTM-1525 > URL: https://issues.jboss.org/browse/JBTM-1525 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > We have a lot of version numbers scattered throughout our poms. Most of which should be in the root pom. This task is to hunt them all down and move the versions into the root. > I think this finds them: > {code} > grep -r "<version>" **/*/pom.xml > {code} > Not sure if it gets them all. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1525) Remove version numbers from all but parent pom

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1525?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1525: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/290 > Remove version numbers from all but parent pom > ---------------------------------------------- > > Key: JBTM-1525 > URL: https://issues.jboss.org/browse/JBTM-1525 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Paul Robinson > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.0.0.M3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > We have a lot of version numbers scattered throughout our poms. Most of which should be in the root pom. This task is to hunt them all down and move the versions into the root. > I think this finds them: > {code} > grep -r "<version>" **/*/pom.xml > {code} > Not sure if it gets them all. -- 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, 4 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 May 2013