July 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Created: (JBTM-863) Move hudson based XTS tests into AS7 integration test suite

by Andrew Dinn (JIRA)

Move hudson based XTS tests into AS7 integration test suite ----------------------------------------------------------- Key: JBTM-863 URL: https://issues.jboss.org/browse/JBTM-863 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: XTS Reporter: Andrew Dinn The XTS unit and interop tests are currently run as a hudson job. Thsi is because they need to run in a container with a full WS stack available. It would be better if all or, at least, some of these tests were included in the AS7 integration test suite, most likely using Arquilian to manage deployment of the test wars to AS7. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBTM-874) Move XTS demo docs into "Transactions XTS Administration And Development Guide"

by Paul Robinson (JIRA)

Move XTS demo docs into "Transactions XTS Administration And Development Guide" -------------------------------------------------------------------------------- Key: JBTM-874 URL: https://issues.jboss.org/browse/JBTM-874 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M1 ...as a new chapter. This improves consistency and maintainability. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBTM-817) Automate execution of XTS crash recovery tests

by Andrew Dinn (JIRA)

Automate execution of XTS crash recovery tests ---------------------------------------------- Key: JBTM-817 URL: https://jira.jboss.org/browse/JBTM-817 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.13.0 Reporter: Andrew Dinn Fix For: 4.15.0 The XTS codebase includes crash recovery tests in the sar/tests subtree which currently need to be executed manually. This needs to be changed so that the current tests can be run automatically via Hudson. After this has been completed it should then be possible to extend the test suite to exercise scenarios not yet covered by the current range of tests. The tests themselves employ a web service client and several web services which are deployed to the app server with the test code. The behaviour of the client and web services can be scripted so this single deployment is capable of exercising all the scenarios which are required in order to lead up to a crash. However, automation is not straightforward for several reasons: Execution of the tests requires starting up an app server twice, the first time so that it can be crashed at a specific point during execution then a second time so that recovery processing can be checked. The JBossTS codebase includes some utilities which can be used to help manage startup and shutdown of the JBoss AS instance. Crashing of the app server and tracing of execution during the first and second runs requires the use of the Byteman agent and Byteman rules. Suitable Byteman rule scripts exist for all the current tests, However, trace output is currently written to a file and the output is verified by eyeball. Timing variations mean that this output does not always have a fixed format. Also, validation requires checking that identifiers printed during the first and second run match up. It would be worth investigating an alternative way of collecting and validating this trace information e.g. using the dtest package contributed to Byteman by Jonathan Halliday. dtest has been used to test similar scenarios in the JBossTS JTA - XTS bridge code (the latter is in the txbridge source tree). Timing variations also mean that execution of recovery code may needs to be manipulated using Byteman rules in order to ensure that the circumstances specified in the test scenario are actually met. This can involve introducing delays or dropping messages to ensure that events are handled in a specific order. The existing Bbyteman scripts include rules to achieve this where needed by the current tests. However, once again, this complicates automation of the trace validation process since it requires some of the traced operations to be discounted until an occurrence which has been engineered is identified. In the longer run the tests will need to be extended in two dimensions. Firstly, the current test locates the client, web services and transaction coordinator in one application server. The client, web services and transaction coordinator need to be tested when they are deployed in different app servers in various possible combinations and the correct handling of a crash by one or more of these app servers needs to be validated. Secondly, the current tests only test normal recovery situations. It will also be necessary to simulate failures in the recovery process, either by scripting the web service behaviour or by injecting faults using Byteman rules. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

8
17
0 / 0

[JBoss JIRA] (JBTM-1180) quickstarts/pom.xml specifies duplicate child module TXBridge

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1180: ----------------------------------- Summary: quickstarts/pom.xml specifies duplicate child module TXBridge Key: JBTM-1180 URL: https://issues.jboss.org/browse/JBTM-1180 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 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-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-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] (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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2012