May 2012 - jbossts-issues - Jboss List Archives

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

5
18
0 / 0

[JBoss JIRA] (JBTM-1165) XTS crash rec tests: change AS7 dependency version in pom.xml from SNAPSHOT to Final

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1165: ----------------------------------- Summary: XTS crash rec tests: change AS7 dependency version in pom.xml from SNAPSHOT to Final Key: JBTM-1165 URL: https://issues.jboss.org/browse/JBTM-1165 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, XTS Affects Versions: 4.16.4 Reporter: Ivo Studensky Assignee: Ivo Studensky Priority: Minor Fix For: 4.16.5 The current version of AS7 dependencies in the XTS crash rec tests contains -SNAPSHOT which makes troubles in testing on Hudson. This needs to be fixed by changing the version to 7.1.1.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, 8 months

3
5
0 / 0

[JBoss JIRA] (JBTM-1170) Maven part of build.xml of txbridge tests does not work on MS Windows system

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1170: ----------------------------------- Summary: Maven part of build.xml of txbridge tests does not work on MS Windows system Key: JBTM-1170 URL: https://issues.jboss.org/browse/JBTM-1170 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.16.4 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.16.5 A maven part of build.xml file in txbridge/tests does not work on MS Windows platforms due to a typo in maven execution command. There should be: <exec executable="cmd" dir="${basedir}" failonerror="true"> instead of <exec executable="mvn" dir="${basedir}" failonerror="true"> -- 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, 8 months

3
11
0 / 0

[JBoss JIRA] (JBTM-1151) xaResourceRecordWrappingPluginClassName won't get set from property

by xexplorer (JIRA)

xexplorer created JBTM-1151: ------------------------------- Summary: xaResourceRecordWrappingPluginClassName won't get set from property Key: JBTM-1151 URL: https://issues.jboss.org/browse/JBTM-1151 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTA Affects Versions: 4.16.3 Reporter: xexplorer Assignee: Tom Jenkinson field name xaResourceRecordWrappingPluginClassName in com.arjuna.ats.jta.common.JTAEnvironmentBean with incorrect setter and getter name. So this field can't be initialized by BeanPopulator. The setter name need to be changed to setXaResourceRecordWrappingPluginClassName, and getter name should getXaResourceRecordWrappingPluginClassName -- 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, 8 months

4
8
0 / 0

[JBoss JIRA] (JBTM-1160) NoClassDefFoundError for Logging related packages when jbossjts is started in standalone mode.

by Kamala Sreenivasan (JIRA)

Kamala Sreenivasan created JBTM-1160: ---------------------------------------- Summary: NoClassDefFoundError for Logging related packages when jbossjts is started in standalone mode. Key: JBTM-1160 URL: https://issues.jboss.org/browse/JBTM-1160 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.16.4 Environment: Windows Reporter: Kamala Sreenivasan Assignee: Tom Jenkinson Priority: Minor When the start-transaction-service-bat is run, then the following exceptions are thrown Exception - NoClassDefFoundError - org/jboss/logging/Logger Reason - The jboss-logging.jar is not in classpath Solution - This file is present in the lib\ext folder of $JBOSSTS_HOME. Add it to the classpath Exception - NoClasDefFoundError - org/sl4j/LoggerFactory Reason - The sl4j jars are not present in the classpath Solution - Add the slf4j-api-1.5.6.jar and slf4j-jdk14-1.5.6.jar present in the $JBOSSTS_HOME\jacorb\lib folder to the classpath Note - logkit-1.2.jar is present in the classpath. The sl4j jars should replace the logkit-1.2.jar These above items can be updated in the setup-env.bat file Add the following in the setup-env.bat file -------------------------------------------------------------------------------------------------------------------------------- set EXT_CLASSPATH=%EXT_CLASSPATH%;%JBOSSTS_HOME%\lib\ext\jboss-logging.jar set JACORB_CLASSPATH=%JACORB_CLASSPATH%;%JACORB_HOME%\lib\slf4j-jdk14-1.5.6.jar set JACORB_CLASSPATH=%JACORB_CLASSPATH%;%JACORB_HOME%\lib\slf4j-api-1.5.6.jar -------------------------------------------------------------------------------------------------------------------------------- -- 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, 8 months

3
3
0 / 0

[JBoss JIRA] (JBTM-1173) Add IPv6 support to XTS demo tests and TxBridge demo tests

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1173: ----------------------------------- Summary: Add IPv6 support to XTS demo tests and TxBridge demo tests Key: JBTM-1173 URL: https://issues.jboss.org/browse/JBTM-1173 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Testing, TxBridge, XTS Affects Versions: 4.16.4 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.16.5 We need to test the XTS demo app and TxBridge demo app on IPv6, hence we need to change the XTS demo tests and TxBridge demo tests to support IPv6. -- 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, 8 months

4
17
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2012