June 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-631) Generate proper maven artefacts

by Thomas Diesler (JIRA)

Generate proper maven artefacts ------------------------------- Key: JBTM-631 URL: https://jira.jboss.org/jira/browse/JBTM-631 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler The artefacts under jbossts (http://repository.jboss.org/maven2/jboss/jbossts/jbossjta) don't seem to be in sync with the project releases. * jbossjta-4.4.0.GA being the latest -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
6
0 / 0

[JBoss JIRA] (JBTM-1146) XTS Demo: ServiceStateManager fails to rollback during recovery as TXID is not known.

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1146: ----------------------------------- Summary: XTS Demo: ServiceStateManager fails to rollback during recovery as TXID is not known. Key: JBTM-1146 URL: https://issues.jboss.org/browse/JBTM-1146 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.5, 5.0.0.M2 See: http://172.17.131.2/job/btny-quickstarts/108/consoleText In particular, notice the NPE from: {code} /** * release a derived state previously stored using the transaction id as a lookup key * @param txId the id of the transaction which created the derived state */ protected void removeState(Object txId) { transactions.remove(txId); } {code} I don't yet know: A) If recovery should even be happening in this part of the test. B) Assuming recovery should happen, I don't know if the outcome should be rollback; which is what it looks like is happening here. -- 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, 6 months

3
16
0 / 0

[JBoss JIRA] (JBTM-1128) Could not invoke deployment method: BaseCrashTest.createTestArchive()

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1128: ----------------------------------- Summary: Could not invoke deployment method: BaseCrashTest.createTestArchive() Key: JBTM-1128 URL: https://issues.jboss.org/browse/JBTM-1128 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.16.3 Reporter: Paul Robinson Assignee: Paul Robinson It looks like there was a problem generating the Shrinkwrap archive from the xtstest.war artefact. {code} Results : Tests in error: com.arjuna.qa.junit.TestBASubordinateCrashDuringCommitAfterSubordinateExit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATCrashDuringOnePhaseCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestBACrashDuringOnePhaseCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATSubordinateCrashDuringCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATParticipantCrashAndRecover: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestBASubordinateCrashDuringCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATSubordinateCrashDuringPrepare: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestBASubordinateCrashDuringComplete: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATHeuristicRecoveryAfterDelayedCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestBACrashDuringCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() com.arjuna.qa.junit.TestATCrashDuringCommit: Could not invoke deployment method: public static org.jboss.shrinkwrap.api.Archive com.arjuna.qa.junit.BaseCrashTest.createTestArchive() {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, 6 months

2
7
0 / 0

[JBoss JIRA] (JBTM-1072) Get hudson to add a comment on pull requests after doing a build

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1072: ----------------------------------- Summary: Get hudson to add a comment on pull requests after doing a build Key: JBTM-1072 URL: https://issues.jboss.org/browse/JBTM-1072 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.Final -- 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, 6 months

2
18
0 / 0

[JBoss JIRA] (JBTM-1078) Failure to parse default-jbossts-properties.xml on JBossAS boot

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1078: ----------------------------------- Summary: Failure to parse default-jbossts-properties.xml on JBossAS boot Key: JBTM-1078 URL: https://issues.jboss.org/browse/JBTM-1078 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Tom Jenkinson Priority: Blocker Fix For: 4.16.3 To reproduce: # cd to 4.16.3 tag of narayana # Set version to 4.16.3.Final in the build.xml # ant -Dpublican=false -DskipTests=true # ant mvn-local-repository # Download JBossAS 7.1.1 from https://github.com/jbossas/jboss-as/zipball/7.1.1.Final # unzip # edit pom.xml and set jbossts version to 4.16.3.Final # mvn install -DskipTests=true # cd ./build/target/jboss-as-7.1.1.Final # sh bin/standalone.sh Observe boot error: {code} 7:51:54,694 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 57) JBAS014612: Operation ("add") failed - address: ([("subsystem" => "transactions") ang.RuntimeException: java.lang.RuntimeException: unable to load properties from jar:file:/tmp/jboss-as-7.1.1.Final/build/target/jboss-as-7.1.1.Final/modules/org/jboss/jts/main/jbossjts-4.16.3.Final.jar!/default-jbossts-properties.xml at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:81) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance(BeanPopulator.java:49) at com.arjuna.ats.arjuna.common.arjPropertyManager.getCoreEnvironmentBean(arjPropertyManager.java:45) at org.jboss.as.txn.service.CoreEnvironmentService.getValue(CoreEnvironmentService.java:53) at org.jboss.as.txn.service.CoreEnvironmentService.setProcessImplementation(CoreEnvironmentService.java:102) at org.jboss.as.txn.subsystem.TransactionSubsystemAdd.performCoreEnvironmentBootTime(TransactionSubsystemAdd.java:309) at org.jboss.as.txn.subsystem.TransactionSubsystemAdd.performBoottime(TransactionSubsystemAdd.java:172) at org.jboss.as.controller.AbstractBoottimeAddStepHandler.performRuntime(AbstractBoottimeAddStepHandler.java:57) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:311) [jboss-as-controller-7.1.1.Final.jar:7.1.1.Final] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] Caused by: java.lang.RuntimeException: unable to load properties from jar:file:/tmp/jboss-as-7.1.1.Final/build/target/jboss-as-7.1.1.Final/modules/org/jboss/jts/main/jbossjts-4.16.3.Final.jar !/default-jbossts-properties.xml at com.arjuna.common.util.propertyservice.PropertiesFactory.getPropertiesFromFile(PropertiesFactory.java:110) at com.arjuna.common.util.propertyservice.PropertiesFactory.initDefaultProperties(PropertiesFactory.java:236) at com.arjuna.common.util.propertyservice.PropertiesFactory.getDefaultProperties(PropertiesFactory.java:66) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:77) at com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance(BeanPopulator.java:77) ... 16 more Caused by: java.lang.IllegalArgumentException: Invalid index 0; current element has only 0 attributes at com.ctc.wstx.sr.AttributeCollector.throwIndex(AttributeCollector.java:1018) at com.ctc.wstx.sr.AttributeCollector.getValue(AttributeCollector.java:355) at com.ctc.wstx.sr.BasicStreamReader.getAttributeValue(BasicStreamReader.java:607) at com.arjuna.common.util.propertyservice.PropertiesFactory.loadFromXML(PropertiesFactory.java:188) at com.arjuna.common.util.propertyservice.PropertiesFactory.loadFromFile(PropertiesFactory.java:145) at com.arjuna.common.util.propertyservice.PropertiesFactory.getPropertiesFromFile(PropertiesFactory.java:106) ... 19 more {code} This looks to me like it was caused by [JBTM-1054]. I suspect there is an unexpected XML block present in jar:file:/tmp/jboss-as-7.1.1.Final/build/target/jboss-as-7.1.1.Final/modules/org/jboss/jts/main/jbossjts-4.16.3.Final.jar!/default-jbossts-properties.xml. For example one with a missing value. I've tried commenting out keys with empty values, but that didn't help. It's not clear to me from debugging the code, which element it is complaining about. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBTM-659) support ipv6

by Jonathan Halliday (JIRA)

support ipv6 ------------ Key: JBTM-659 URL: https://jira.jboss.org/jira/browse/JBTM-659 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.10.0 The changes to Uid in JBTM-522 pave the way for full IPv6 support in the codebase. Although ad-hoc testing gives good results, we really need to modify the test setup and servers to ensure a reasonable subset of tests are run on IPv6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

5
22
0 / 0

[JBoss JIRA] (JBTM-1149) Add some qa tests for the none-socket recovery manager

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1149: ----------------------------------- Summary: Add some qa tests for the none-socket recovery manager Key: JBTM-1149 URL: https://issues.jboss.org/browse/JBTM-1149 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Reporter: Tom Jenkinson Assignee: Michael Musgrove txcore_recovery Crash rec 9/10 iirc -- 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, 7 months

2
3
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, 7 months

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, 7 months

5
18
0 / 0

[JBoss JIRA] (JBTM-1185) @WebService annotation is missing targetNamespace in outbound.service.TestServiceImpl class

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1185: ----------------------------------- Summary: @WebService annotation is missing targetNamespace in outbound.service.TestServiceImpl class Key: JBTM-1185 URL: https://issues.jboss.org/browse/JBTM-1185 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, TxBridge Affects Versions: 4.16.4 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.16.5 TestServiceImpl class from org.jboss.jbossts.txbridge.tests.outbound.service packages contains empty @WebService annotation which makes troubles on IBM JDK 7. Add targetNamespace parameter to that annotation to fix the issue. -- 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, 7 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues June 2012