September 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1239) XTS and TXBridge Demo: java.lang.NoClassDefFoundError: com/arjuna/wst/SystemException

by Amos Feng (JIRA)

Amos Feng created JBTM-1239: ------------------------------- Summary: XTS and TXBridge Demo: java.lang.NoClassDefFoundError: com/arjuna/wst/SystemException Key: JBTM-1239 URL: https://issues.jboss.org/browse/JBTM-1239 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Demonstrator Affects Versions: 5.0.0.M1 Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.0.0.M2 working OK with jboss-as-7.1.1.Final but failed with our 5_BRANCH jboss-as-7.2.0.Alpha1-SNAPSHOT Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class com.jboss.jbosstm.xts.demo.services.theatre.TheatreServiceBA with ClassLoader ModuleClassLoader for Module \"deployment.xts-demo.ear.xts-demo-war-5.0.0.M2-SNAPSHOT.war:main\" from Service Module Loader Caused by: java.lang.NoClassDefFoundError: com/arjuna/wst/SystemException in jboss-as-7.2.0.Alpha1-SNAPSHOT, it deploys xts-demo-war which miss the dependency before xts-demo-webservices. so it looks like we need to specify the order of war in xts-demo.ear -- 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
5
0 / 0

[JBoss JIRA] (JBTM-1256) jbossts-branch417-EAP61-ipv6-dualstack is running the DB QA tests

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1256: ----------------------------------- Summary: jbossts-branch417-EAP61-ipv6-dualstack is running the DB QA tests Key: JBTM-1256 URL: https://issues.jboss.org/browse/JBTM-1256 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.0, 5.0.0.M2 jbossts-branch417-EAP61-ipv6-dualstack is running junit-jdbc-ncl-testsuite, which I beleive it should not as we don't have any IPv6 databases. http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-branch417-EAP61-ip... -- 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

1
4
0 / 0

[JBoss JIRA] (JBTM-1229) Implement draft 8 of the REST-tx specification

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-1229: -------------------------------------- Summary: Implement draft 8 of the REST-tx specification Key: JBTM-1229 URL: https://issues.jboss.org/browse/JBTM-1229 Project: JBoss Transaction Manager Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: REST Affects Versions: 5.0.0.M1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Minor Fix For: 4.17.0 Implement draft 8 of the REST-AT specification. Make sure rest-tx/docs is updated with the latest draft. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

2
2
0 / 0

[JBoss JIRA] (JBTM-1212) update arquillian to use standalone-xts.xml from standalone/configuration

by Amos Feng (JIRA)

Amos Feng created JBTM-1212: ------------------------------- Summary: update arquillian to use standalone-xts.xml from standalone/configuration Key: JBTM-1212 URL: https://issues.jboss.org/browse/JBTM-1212 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Affects Versions: 5.0.0.M1, 4.16.4 Reporter: Amos Feng Assignee: Amos Feng Fix For: 4.16.5, 5.0.0.M2 It might be a bug when load configuration not in <jboss_home>/standalone/configuration. so alert with the following steps: 1.cp <jboss-as>/docs/examples/configs/standalone-xts.xml <jboss-as>/standalone/configs/ 2.sh bin/standalone.sh --server-config=standalone-xts.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

3
16
0 / 0

[JBoss JIRA] (JBTM-1248) Remove XTS sar

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1248: ----------------------------------- Summary: Remove XTS sar Key: JBTM-1248 URL: https://issues.jboss.org/browse/JBTM-1248 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Reporter: Tom Jenkinson Assignee: Paul Robinson Do we still need XTS/sar/? If it has been re-purposed, do we still need XTS/sar/assembly/sar.xml? -- 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
7
0 / 0

[JBoss JIRA] (JBTM-1136) XTS Crash Recovery fail: Could not start container

by Amos Feng (JIRA)

Amos Feng created JBTM-1136: ------------------------------- Summary: XTS Crash Recovery fail: Could not start container Key: JBTM-1136 URL: https://issues.jboss.org/browse/JBTM-1136 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Amos Feng Assignee: Tom Jenkinson http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/193 http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java6/194 http://albany/view/Narayana+BlackTie/job/jbossts-branch416-java7/137 It looks like booting jboss-as with the following error and xtstests.war can not be deployed. the arquillian thinks the container does not start. {code} 02:51:57,012 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 50) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "osgi")]): org.jboss.msc.service.DuplicateServiceException: Service jbosgi.integration.PersistentBundlesHandler is already registered at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:154) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:227) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:560) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:955) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.osgi.service.PersistentBundlesIntegration.addService(PersistentBundlesIntegration.java:76) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.osgi.parser.OSGiSubsystemAdd$2.execute(OSGiSubsystemAdd.java:130) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.osgi.parser.OSGiSubsystemAdd$1.execute(OSGiSubsystemAdd.java:103) [jboss-as-osgi-service-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:311) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_03] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_03] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_03] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

3
20
0 / 0

[JBoss JIRA] (JBTM-940) Fix intermittant qa quite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2

by Tom Jenkinson (Created) (JIRA)

Fix intermittant qa quite failure: org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 --------------------------------------------------------------------------------------------------- Key: JBTM-940 URL: https://issues.jboss.org/browse/JBTM-940 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Fix For: 4.15.x, 5.0.0.M2 Assuming failure in test, rather than failed test: jbossts-trunk-java6 - Build # 925 - Still Failing! [junit] Test org.jboss.jbossts.qa.junit.testgroup.TestGroup_crashrecovery05_2 FAILED -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

5
18
0 / 0

[JBoss JIRA] (JBTM-1219) WS-CF & WSTX IPv6 tests fail: narayana-jts-5.0.0.M2-SNAPSHOT.jar; cannot read zip file

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1219: ----------------------------------- Summary: WS-CF & WSTX IPv6 tests fail: narayana-jts-5.0.0.M2-SNAPSHOT.jar; cannot read zip file Key: JBTM-1219 URL: https://issues.jboss.org/browse/JBTM-1219 Project: JBoss Transaction Manager Issue Type: Sub-task Security Level: Public (Everyone can see) Components: XTS Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.0, 5.0.0.M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years

1
4
0 / 0

[JBoss JIRA] (JBTM-1254) Simplify narayana.sh by removing ability to have empty IPV6_OPTS

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1254: ----------------------------------- Summary: Simplify narayana.sh by removing ability to have empty IPV6_OPTS Key: JBTM-1254 URL: https://issues.jboss.org/browse/JBTM-1254 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.17.0, 5.0.0.M2 We currently use [ -z "${VAR+c}" ] notation to detect if a variable has been set, allowing for it being set to the empty string. Here's an example: {code} # if IPV6_OPTS is not set get the jdbc drivers (we do not run the jdbc tests in IPv6 mode) [ -z "${IPV6_OPTS+x}" ] && ant -DisIdlj=$IDLJ "$QA_BUILD_ARGS" get.drivers dist || ant -DisIdlj=$IDLJ "$QA_BUILD_ARGS" dist {code} The problem with this approach is that it's rather cryptic to understand what's going on. This makes it hard to read and easy to create a bug. We've had two bugs so far, due to this syntax. By removing the ability to "export IPV6_OPTS=", we can simplify these portions of the script to look like: {code} if [ "${IPV6_OPTS}" = "" ]; then ant -DisIdlj=$IDLJ "$QA_BUILD_ARGS" get.drivers dist else ant -DisIdlj=$IDLJ "$QA_BUILD_ARGS" dist fi {code} Which is a lot easier to read and much less error-prone. Should we ever need to enable IPv6 without setting any IPv6 options, we could either re-instate the old code, or set a dummy option. -- 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

3
8
0 / 0

[JBoss JIRA] (JBTM-1242) narayana-java7 job hung for 4d 10hr

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1242: ----------------------------------- Summary: narayana-java7 job hung for 4d 10hr Key: JBTM-1242 URL: https://issues.jboss.org/browse/JBTM-1242 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Tom Jenkinson Fix For: 4.17.0, 5.0.0.M2 http://172.17.131.2/job/narayana-java7/441/ -- 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
2
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2012