May 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1675) integration-tests test 215 failed

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1675?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1675: ---------------------------- Attachment: test-215-130503092057-out.txt > integration-tests test 215 failed > --------------------------------- > > Key: JBTM-1675 > URL: https://issues.jboss.org/browse/JBTM-1675 > 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 > > Attachments: test-215-130503092057-out.txt > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1502 -- 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-1675) integration-tests test 215 failed

by Amos Feng (JIRA)

Amos Feng created JBTM-1675: ------------------------------- Summary: integration-tests test 215 failed Key: JBTM-1675 URL: https://issues.jboss.org/browse/JBTM-1675 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/view/Narayana+BlackTie/job/blacktie-linux64/1502 -- 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=12429120&page=... ] Gytis Trikleris logged work on JBTM-1365: ----------------------------------------- Author: Gytis Trikleris Created on: 03/May/13 5:06 AM Start Date: 03/May/13 5:06 AM Worklog Time Spent: 6 hours Issue Time Tracking ------------------- Remaining Estimate: 2 weeks, 50 minutes (was: 2 weeks, 6 hours, 50 minutes) Time Spent: 4 days, 7 hours, 10 minutes (was: 4 days, 1 hour, 10 minutes) Worklog Id: (was: 12429120) > 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: 4 days, 7 hours, 10 minutes > Remaining Estimate: 2 weeks, 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-1674) btadmin.PauseDomainTest failed with command failure

by Amos Feng (JIRA)

Amos Feng created JBTM-1674: ------------------------------- Summary: btadmin.PauseDomainTest failed with command failure Key: JBTM-1674 URL: https://issues.jboss.org/browse/JBTM-1674 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/view/Narayana+BlackTie/job/blacktie-linux64/1501 {noformat} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.blacktie.btadmin.PauseDomainTest ------------------------------------------------------------------------------- Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 83.154 sec <<< FAILURE! testPauseDomainWithArg(org.jboss.narayana.blacktie.btadmin.PauseDomainTest) Time elapsed: 53.947 sec <<< FAILURE! junit.framework.AssertionFailedError: Command failed at junit.framework.Assert.fail(Assert.java:47) at org.jboss.narayana.blacktie.btadmin.PauseDomainTest.setUp(PauseDomainTest.java:48) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:98) at org.apache.maven.surefire.junit.JUnit3Provider.executeTestSet(JUnit3Provider.java:107) at org.apache.maven.surefire.junit.JUnit3Provider.invoke(JUnit3Provider.java:84) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at com.sun.proxy.$Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) {noformat} -- 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-1673) Build failure

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1673?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1673: --------------------------------- no, I think it needs more investigating. > Build failure > ------------- > > Key: JBTM-1673 > URL: https://issues.jboss.org/browse/JBTM-1673 > 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/1492/console -- 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 Ondřej Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-1611?page=com.atlassian.jira.plugin.... ] Ondřej Chaloupka commented on JBTM-1611: ---------------------------------------- Hi, I wonder what I have been doing wrong but I'm not able to run the test without failure. I've tried 3 machines and I'm still getting failures as above. My machine is not such slow (Intel Core i7 2.7GHz, 8GM ram). I've tried to set several values to timeoutFactor but no success here. My steps: # git clone -b 4.17 https://github.com/jbosstm/narayana # cd narayana # ./build.sh -P all -Dmaven.test.skip.exec=true # cd qa # ant dist # redefinition of the TaskImpl.properties - e.g. ## COMMAND_LINE_12=-DCoreEnvironmentBean.timeoutFactor=3 ## COMMAND_LINE_13=-DCoordinatorEnvironmentBean.defaultTimeout=360 # ant -f run-tests.xml -Dtest.name=crashrecovery09 -Dtest.methods=CrashRecovery09_Test01 -Dprofile=hornetq onetest The failure which I'm getting is caused of value 0 set in the valueHolder of Client01a.java. {code} correct = correct && (valueHolder.value == 1); {code} Do you think that I have followed some step incorrectly? Or would you have an idea what to do in other way? Thank you Ondra > 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-1597) xatmi job crashed

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1597?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1597: ------------------------------------- Is this a duplicate of JBTM-1650 do you think? > 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-1673) Build failure

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1673?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1673: ------------------------------------- Ah great, if you think that is all it is feel free to reject the issue and remove the build from CI > Build failure > ------------- > > Key: JBTM-1673 > URL: https://issues.jboss.org/browse/JBTM-1673 > 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/1492/console -- 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-1659) BlackTie build fails when valgrind is not on

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1659: ------------------------------------- (Also, please can you delete the jobs from hudson now you have resolved the issue? Thanks!) > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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-1659) BlackTie build fails when valgrind is not on

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1659?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on JBTM-1659: ------------------------------------- Ah great, I saw this message which checking in to say that I had seen all the jobs I had set up pass! Thanks for checking > BlackTie build fails when valgrind is not on > -------------------------------------------- > > Key: JBTM-1659 > URL: https://issues.jboss.org/browse/JBTM-1659 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Critical > Fix For: 5.0.0.M3 > > > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux32/925/ > http://172.17.131.2/view/Narayana+BlackTie/job/blacktie-linux64/1489/ -- 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