August 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1179) TXBridge demo test fails due to: IllegalArgumentException: nodeName is empty, or just whitespace

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1179: ----------------------------------- Summary: TXBridge demo test fails due to: IllegalArgumentException: nodeName is empty, or just whitespace Key: JBTM-1179 URL: https://issues.jboss.org/browse/JBTM-1179 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Amos Feng Fix For: 5.0.0.M2 To reproduce: Checkout the Narayana quickstarts prject. {code} cd XTS mvn install cd ../TXBridge mvn install {code} Observe: {code} 16:33:00,202 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/../service/target/txbridge-demo-service] startup failed due to previous errors: java.lang.Ille galArgumentException: nodeName is empty, or just whitespace at org.jboss.logmanager.LoggerNode.<init>(LoggerNode.java:127) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:154) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LoggerNode.getOrCreate(LoggerNode.java:163) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LogContext.getLogger(LogContext.java:126) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LogManager.getLogger(LogManager.java:401) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logmanager.LogManager.getLogger(LogManager.java:45) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at java.util.logging.LogManager.demandLogger(LogManager.java:389) [rt.jar:1.6.0_30] at java.util.logging.Logger.getLogger(Logger.java:288) [rt.jar:1.6.0_30] at org.jboss.logmanager.Logger.getLogger(Logger.java:59) [jboss-logmanager-1.3.1.Final.jar:1.3.1.Final] at org.jboss.logging.JBossLogManagerProvider.doGetLogger(JBossLogManagerProvider.java:56) [jboss-logging-3.1.1.GA.jar:3.1.1.GA] at org.jboss.logging.JBossLogManagerProvider.getLogger(JBossLogManagerProvider.java:47) [jboss-logging-3.1.1.GA.jar:3.1.1.GA] at org.jboss.logging.Logger.getLogger(Logger.java:2163) [jboss-logging-3.1.1.GA.jar:3.1.1.GA] at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:409) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3765) at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) 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] {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

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBTM-1177) The TXBridge demo-test fails to find required build artifacts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1177: ----------------------------------- Summary: The TXBridge demo-test fails to find required build artifacts Key: JBTM-1177 URL: https://issues.jboss.org/browse/JBTM-1177 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This is because it was not updated when it was moved into the quickstart project. -- 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

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (JBTM-1178) The TXBridge demo is not tested by "mvn test" in the root of the quickstart project

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1178: ----------------------------------- Summary: The TXBridge demo is not tested by "mvn test" in the root of the quickstart project Key: JBTM-1178 URL: https://issues.jboss.org/browse/JBTM-1178 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This is because it was not updated when it was moved into the quickstart project. -- 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

12 years, 1 month

2
4
0 / 0

[JBoss JIRA] (JBTM-1141) Enable TXBridge tests in trunk

by Tom Jenkinson (JIRA)

Tom Jenkinson created JBTM-1141: ----------------------------------- Summary: Enable TXBridge tests in trunk Key: JBTM-1141 URL: https://issues.jboss.org/browse/JBTM-1141 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Reporter: Tom Jenkinson Assignee: Paul Robinson txbridge is being tested in the branch but not in trunk as some of the steps required are not converted yet so surefire is disabled in: txbridge/pom.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

12 years, 1 month

1
6
0 / 0

[JBoss JIRA] (JBTM-1057) Port TXBridge demo tests to quickstarts/txbridge/demo

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1057: ----------------------------------- Summary: Port TXBridge demo tests to quickstarts/txbridge/demo Key: JBTM-1057 URL: https://issues.jboss.org/browse/JBTM-1057 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2, 5.0.0.M3 Currently the TXBridge demo tests are only in the 4.16 branch. Here they live in the JBossTS project and pull in built artefacts for, txbridge-demo-service.jar, txbridge-demo-client.war and xts-demo.ear. see here: https://svn.jboss.org/repos/labs/labs/jbosstm/branches/JBOSSTS_4_16/txbri... The TXBridge demo has been moved, in trunk, to the quickstarts project. Therefore the built artefact of the XTS demo will not be available. We need to figure out a way of pulling this in. Maybe we could pull in the XTS demo as a maven artefact? Alternately, we could remove the dependency on the XTS demo by re-creating the Restaurant service in the TXBridge demo. Also, it doesn't seem right, that built txbridge-demo artefacts are required. Wouldn't it be better for shrinkwrap to create these? The reason why these artefacts where used in 4.16, was to fit in with the existing layout and build system. In trunk we are using maven throughout and can make more disruptive changes, so we should try and get this test right. -- 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

12 years, 1 month

2
11
0 / 0

[JBoss JIRA] (JBTM-1035) Move TXBridge demo to quickstarts git repo

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1035: ----------------------------------- Summary: Move TXBridge demo to quickstarts git repo Key: JBTM-1035 URL: https://issues.jboss.org/browse/JBTM-1035 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-888) Update TXBridge demo to support JBoss AS 7.0.1

by Paul Robinson (JIRA)

Update TXBridge demo to support JBoss AS 7.0.1 ---------------------------------------------- Key: JBTM-888 URL: https://issues.jboss.org/browse/JBTM-888 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.15.4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
9
0 / 0

[JBoss JIRA] (JBTM-1034) Convert the TXBridge demo project from ant to maven

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1034: ----------------------------------- Summary: Convert the TXBridge demo project from ant to maven Key: JBTM-1034 URL: https://issues.jboss.org/browse/JBTM-1034 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: TxBridge Affects Versions: 5.0.0.M1 Reporter: Paul Robinson Assignee: Paul Robinson 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: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBTM-901) Classloading exceptions during the periodic recovery process

by Ivo Studensky (JIRA)

Classloading exceptions during the periodic recovery process ------------------------------------------------------------ Key: JBTM-901 URL: https://issues.jboss.org/browse/JBTM-901 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge Affects Versions: 4.15.3 Reporter: Ivo Studensky Assignee: Paul Robinson Some classloading exceptions happen during the periodic recovery process if AS7 started with standalone-xts.xml configuration, see the log snippets bellow. It seems like some missing deps to javax.resource.api and javax.transaction.api in xts module descriptor. But it could also be that the standalone-xts.xml configuration file in AS7 is out of date. Could you check this pls? Note: it was tested on the latest AS7 master. {code} 13:08:17,500 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" java.lang.NoClassDefFoundError: javax/transaction/SystemException 13:08:17,500 ERROR [stderr] (Periodic Recovery) at org.jboss.jbossts.txbridge.outbound.OutboundBridgeRecoveryManager.periodicWorkSecondPass(OutboundBridgeRecoveryManager.java:87) 13:08:17,501 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) 13:08:17,501 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) 13:08:17,501 ERROR [stderr] (Periodic Recovery) Caused by: java.lang.ClassNotFoundException: javax.transaction.SystemException from [Module "org.jboss.xts:main" from local module loader @2ca6d51e (roots: /home/studensky/job/git/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/modules)] 13:08:17,501 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:191) 13:08:17,501 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:361) 13:08:17,501 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:333) 13:08:17,502 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:310) 13:08:17,502 ERROR [stderr] (Periodic Recovery) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:103) 13:08:17,502 ERROR [stderr] (Periodic Recovery) ... 3 more {code} {code} Exception in thread "Periodic Recovery" java.lang.NoClassDefFoundError: javax/resource/spi/XATerminator 13:18:56,834 ERROR [stderr] (Periodic Recovery) at org.jboss.jbossts.txbridge.inbound.InboundBridgeRecoveryManager.getIndoubtSubordinates(InboundBridgeRecoveryManager.java:227) 13:18:56,834 ERROR [stderr] (Periodic Recovery) at org.jboss.jbossts.txbridge.inbound.InboundBridgeRecoveryManager.periodicWorkSecondPass(InboundBridgeRecoveryManager.java:196) 13:18:56,834 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) 13:18:56,835 ERROR [stderr] (Periodic Recovery) at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (JBTM-1012) fix exception use in FileSystemStore.closeAndUnlock

by Jonathan Halliday (Created) (JIRA)

fix exception use in FileSystemStore.closeAndUnlock --------------------------------------------------- Key: JBTM-1012 URL: https://issues.jboss.org/browse/JBTM-1012 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Core Affects Versions: 5.0.0.M1, 4.16.0.Final Reporter: Jonathan Halliday Assignee: Jonathan Halliday Fix For: 4.16.1, 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

12 years, 1 month

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2012