September 2013 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1898) UndeclaredThrowableException in CompensatableTest.testNeverExistingTX

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1898?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-1898: --------------------------------- yeah, I will take a look at the rules > UndeclaredThrowableException in CompensatableTest.testNeverExistingTX > --------------------------------------------------------------------- > > Key: JBTM-1898 > URL: https://issues.jboss.org/browse/JBTM-1898 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.0.0.M5 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana-codeCoverage/68/c... > {code} > [0mAug 23, 2013 8:06:55 PM org.jboss.arquillian.protocol.jmx.JMXMethodExecutor invoke > SEVERE: Failed: org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.testNeverExistingTX > java.lang.reflect.UndeclaredThrowableException > at $Proxy21.runTestMethod(Unknown Source) > at org.jboss.arquillian.protocol.jmx.JMXMethodExecutor.invoke(JMXMethodExecutor.java:71) > at org.jboss.arquillian.container.test.impl.execution.RemoteTestExecuter.execute(RemoteTestExecuter.java:120) > at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:57) > at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > 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.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: java.io.IOException: Unable to invoke invoke(), status=WAITING > at org.jboss.remotingjmx.protocol.v2.ClientConnection$TheConnection.invoke(ClientConnection.java:1058) > at org.jboss.as.arquillian.container.ManagementClient$MBeanConnectionProxy.invoke(ManagementClient.java:540) > at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:305) > ... 77 more > {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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1913) move the wildfly-blacktie into the narayana repo

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-1913?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-1913: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > move the wildfly-blacktie into the narayana repo > ------------------------------------------------ > > Key: JBTM-1913 > URL: https://issues.jboss.org/browse/JBTM-1913 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BlackTie, Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.0.0.M5 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1561) Cannot create a user defined XATMI service

by Crispin Boylan (JIRA)

[ https://issues.jboss.org/browse/JBTM-1561?page=com.atlassian.jira.plugin.... ] Crispin Boylan updated JBTM-1561: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/428 Remove the need to hardcode the servers and services in the ear file as discussed with tomjenkinson on IRC. > Cannot create a user defined XATMI service > ------------------------------------------ > > Key: JBTM-1561 > URL: https://issues.jboss.org/browse/JBTM-1561 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BlackTie, Documentation > Affects Versions: 5.0.0.M1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 6.0.0.Final > > > The administrative interface, btadmin, does not support the definition of user defined services. Perhaps this functionality was present in the old RHQ interface and was not ported to btadmin when RHQ support was dropped. > The documentation set does not describe how to configure user defined services. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1916) Create parallel CI job for pull requests

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-1916: ------------------------------------- Summary: Create parallel CI job for pull requests Key: JBTM-1916 URL: https://issues.jboss.org/browse/JBTM-1916 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.0.0.M5 -- 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, 2 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 updated JBTM-1645: -------------------------------- Issue Type: Task (was: Feature Request) > 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: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.0.0.M5 > > Original Estimate: 4 hours > Time Spent: 1 hour, 40 minutes > Remaining Estimate: 0 minutes > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1276) utilize existing checkout of jboss-as in narayana.sh rather than blow it away

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1276?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1276: -------------------------------- Issue Type: Task (was: Feature Request) > utilize existing checkout of jboss-as in narayana.sh rather than blow it away > ----------------------------------------------------------------------------- > > Key: JBTM-1276 > URL: https://issues.jboss.org/browse/JBTM-1276 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M2 > > > git fetch > git reset --hard origin/5_BRANCH > git clean -f -d -x > git pull --rebase --ff-only upstream master -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1274) Allows the XTS tests to respect parameters passed in to narayana.sh e.g. skipTests

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1274?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1274: -------------------------------- Issue Type: Task (was: Feature Request) > Allows the XTS tests to respect parameters passed in to narayana.sh e.g. skipTests > ---------------------------------------------------------------------------------- > > Key: JBTM-1274 > URL: https://issues.jboss.org/browse/JBTM-1274 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing, XTS > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.0.0.M2 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1443) Track AS 7.2.0.Alpha1

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1443?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1443: -------------------------------- Issue Type: Task (was: Feature Request) > Track AS 7.2.0.Alpha1 > --------------------- > > Key: JBTM-1443 > URL: https://issues.jboss.org/browse/JBTM-1443 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Application Server Integration > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.0.0.M2 > > > https://issues.jboss.org/browse/AS7/fixforversion/12318469#selectedTab=co... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1283) narayana.sh calls mvn directly, should be build.sh

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1283?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1283: -------------------------------- Issue Type: Task (was: Feature Request) > narayana.sh calls mvn directly, should be build.sh > -------------------------------------------------- > > Key: JBTM-1283 > URL: https://issues.jboss.org/browse/JBTM-1283 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Build System, Testing, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > > The script does this: > function xts_as_tests { > echo "#-1. XTS AS Integration Test" > mvn -f ${WORKSPACE}/jboss-as/testsuite/integration/xts/pom.xml -Pxts.integration.tests.profile "$@" test > [ $? = 0 ] || fatal "XTS AS Integration Test failed" > } > Should probably be this: > function xts_as_tests { > echo "#-1. XTS AS Integration Test" > ./build.sh -f ${WORKSPACE}/jboss-as/testsuite/integration/xts/pom.xml -Pxts.integration.tests.profile "$@" test > [ $? = 0 ] || fatal "XTS AS Integration Test failed" > } -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1196) Cyclic dependency between AS7 and (txframework and XTS)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1196?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1196: -------------------------------- Issue Type: Bug (was: Feature Request) > Cyclic dependency between AS7 and (txframework and XTS) > ------------------------------------------------------- > > Key: JBTM-1196 > URL: https://issues.jboss.org/browse/JBTM-1196 > Project: JBoss Transaction Manager > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: TXFramework, XTS > Reporter: Tom Jenkinson > Assignee: Paul Robinson > Fix For: 5.0.0.M2 > > > Pom uses jboss-as.version which assumes a build of AS7 but in theory that version would not exist until this version of Narayana was released. > At the moment it works because we run against a SNAPSHOT version. > Just brainstorming, but can the tests be ran without AS7 or can XTS be hot deployed by the tests or should these tests be ran in the AS7 test suite? -- 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, 2 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 September 2013