July 2012 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-1140) Update Arquillian version in TxBridge tests, TxBridge demo tests and XTS demo tests

by Ivo Studensky (JIRA)

Ivo Studensky created JBTM-1140: ----------------------------------- Summary: Update Arquillian version in TxBridge tests, TxBridge demo tests and XTS demo tests Key: JBTM-1140 URL: https://issues.jboss.org/browse/JBTM-1140 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Testing, TxBridge, XTS Affects Versions: 4.16.3 Reporter: Ivo Studensky Assignee: Ivo Studensky Fix For: 4.16.4 Arquillian version used in pom.xml's at txbridge tests, txbridge demo tests and xts demo tests are out of date. Please update them to the latest stable ones. -- 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

4
8
0 / 0

[JBoss JIRA] Created: (JBTM-900) Some of XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml

by Ivo Studensky (JIRA)

Some of XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml -------------------------------------------------------------------------------------------- Key: JBTM-900 URL: https://issues.jboss.org/browse/JBTM-900 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: Testing, XTS Affects Versions: 4.15.3 Reporter: Ivo Studensky Some of the XTS unit test EARs contain no longer supported namespace in META-INF/jboss-beans.xml and so they cannot be deployed to AS7. See [1] for the current namespace used in XTS unit test EARs and [2] for the valid namespace that should be used in AS7. A bit weird is that those EARs can be successfully deployed by command line copy and by web admin console, but only deploying by Arquillian uncovered the issue. I've already filed a jira for that - AS7-1927. Please could you take a look at that and fix the namespace? Here is a list of the affected EARs: ws-c-tests.ear ws-t-tests.ear wstx-tests.ear [1] <deployment xmlns="urn:jboss:bean-deployer:2.0"> [2] <deployment xmlns="urn:jboss:pojo:7.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:pojo:7.0 jboss-pojo_7_0.xsd"> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
6
0 / 0

[JBoss JIRA] (JBTM-1015) Reduce recoveryPeriod to 10secs for all XTS crash recovery tests

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1015: ----------------------------------- Summary: Reduce recoveryPeriod to 10secs for all XTS crash recovery tests Key: JBTM-1015 URL: https://issues.jboss.org/browse/JBTM-1015 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.1, 5.0.0.M2 This reduces how long the tests take to run. Any lower than 10secs could result in unwanted behaviour -- 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-1014) RecoveryATCoordinator is named RecoverACCoordinator in XTS crash recovery byteman scripts

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1014: ----------------------------------- Summary: RecoveryATCoordinator is named RecoverACCoordinator in XTS crash recovery byteman scripts Key: JBTM-1014 URL: https://issues.jboss.org/browse/JBTM-1014 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson 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

2
2
0 / 0

[JBoss JIRA] (JBTM-1122) TestBASubordinateCrashDuringComplete does not kill AS

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1122: ----------------------------------- Summary: TestBASubordinateCrashDuringComplete does not kill AS Key: JBTM-1122 URL: https://issues.jboss.org/browse/JBTM-1122 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Tom Jenkinson http://albany/job/narayana-xts-recovery-java6/21/artifact/XTS/sar/crash-r... Notice that the participant is compensated. I think the participant should be closed, but this needs verifying. -- 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
5
0 / 0

[JBoss JIRA] (JBTM-1139) BACrashDuringOnePhaseCommit:SingleCoordinatorCompletionParticipantCloseTest Failed to start

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1139: ----------------------------------- Summary: BACrashDuringOnePhaseCommit:SingleCoordinatorCompletionParticipantCloseTest Failed to start Key: JBTM-1139 URL: https://issues.jboss.org/browse/JBTM-1139 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.4, 5.0.0.M2 Looking at the following log: http://172.17.131.2/view/XTS%20recovery/job/narayana-xts-recovery-java6/8... You will see that the server starts for the first test, but no scenario is ran: {code} 16:37:24,606 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 9755ms - Started 272 of 360 services (87 services are passive or on-demand) 16:37:24,783 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location /home/hudson/workspace/narayana-xts-recovery-java6/jboss-as/build/target/jboss-as-7.1.2.Final-SNAPSHOT/standalone/data/content/9c/b09ed5c8a11739141e8a5b2e5eefb74c508183/content DEBUG [Remoting "endpoint" read-1] (WorkerThread.java:88) org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting "endpoint" read-1', selector sun.nio.ch.EPollSelectorImpl@308bd98e DEBUG [Remoting "endpoint" write-1] (WorkerThread.java:88) org.xnio.nio.WorkerThread.run(WorkerThread.java:88) - Started channel thread 'Remoting "endpoint" write-1', selector sun.nio.ch.EPollSelectorImpl@384f33c1 DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:129) org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:129) - Available version (Versions 0x01) DEBUG [Remoting "endpoint" task-4] (VersionedConectionFactory.java:135) org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:135) - Calling a stable server Apr 23, 2012 4:37:25 PM org.jboss.arquillian.container.test.impl.client.container.ClientContainerController kill INFO: Hard killing of a server instance Apr 23, 2012 4:37:25 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: waiting for byteman to kill server Apr 23, 2012 4:37:36 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:37:47 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:37:58 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:09 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:20 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:31 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:42 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:38:53 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:39:04 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill INFO: jboss-as is alive Apr 23, 2012 4:39:16 PM com.arjuna.qa.extension.JBossAS7ServerKillProcessor kill {code} The trace output for this test is also empty: http://172.17.131.2/view/XTS%20recovery/job/narayana-xts-recovery-java6/8... -- 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-1005) IllegalStateException when deploying TXBridge demo

by Paul Robinson (Created) (JIRA)

IllegalStateException when deploying TXBridge demo -------------------------------------------------- Key: JBTM-1005 URL: https://issues.jboss.org/browse/JBTM-1005 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: TxBridge Affects Versions: 5.0.0.M1, 4.16.0.Beta1 Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.0.Final, 5.0.0.M2 {code} 13:15:07,581 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "txbridge_demo.war" 13:15:07,641 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."txbridge_demo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."txbridge_demo.war".PARSE: Failed to process phase PARSE of deployment "txbridge_demo.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Beta1.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: java.lang.IllegalStateException at org.jboss.as.webservices.util.ASHelper.getRequiredAttachment(ASHelper.java:164) at org.jboss.as.webservices.deployers.WSIntegrationProcessorJAXWS_HANDLER.processAnnotation(WSIntegrationProcessorJAXWS_HANDLER.java:55) at org.jboss.as.webservices.deployers.AbstractIntegrationProcessorJAXWS.deploy(AbstractIntegrationProcessorJAXWS.java:87) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Beta1.jar:] ... 5 more 13:15:07,644 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "txbridge_demo.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"txbridge_demo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"txbridge_demo.war\".PARSE: Failed to process phase PARSE of deployment \"txbridge_demo.war\""}} 13:15:07,650 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) Stopped deployment txbridge_demo.war in 5ms 13:15:07,650 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.deployment.unit."txbridge_demo.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."txbridge_demo.war".PARSE: Failed to process phase PARSE of deployment "txbridge_demo.war" 13:15:07,651 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"txbridge_demo.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"txbridge_demo.war\".PARSE: Failed to process phase PARSE of deployment \"txbridge_demo.war\""}}}} {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

4
4
0 / 0

[JBoss JIRA] (JBTM-1118) com.arjuna.wst.TransactionRolledBackException on BA XTS Crash Recvoery tests

by Amos Feng (JIRA)

Amos Feng created JBTM-1118: ------------------------------- Summary: com.arjuna.wst.TransactionRolledBackException on BA XTS Crash Recvoery tests Key: JBTM-1118 URL: https://issues.jboss.org/browse/JBTM-1118 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.16.3 Reporter: Amos Feng Assignee: Amos Feng Fix For: 4.16.4 there is error when running org.jboss.jbossts.xts.servicetests.test.ba.SingleParticipantCompletionParticipantCloseTest with BACrashDuringOnePhaseCommit.txt 08:52:48,238 ERROR [stderr] (Thread-78) com.arjuna.wst.TransactionRolledBackException 08:52:48,240 ERROR [stderr] (Thread-78) at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) 08:52:48,242 ERROR [stderr] (Thread-78) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) 08:52:48,244 ERROR [stderr] (Thread-78) at org.jboss.jbossts.xts.servicetests.test.ba.SingleParticipantCompletionParticipantCloseTest.run(SingleParticipantCompletionParticipantCloseTest.java:137) 08:52:48,246 ERROR [stderr] (Thread-78) at org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean$1.run(XTSServiceTestRunnerBean.java:115) 08:52:48,248 ERROR [stderr] (Thread-78) org.jboss.jbossts.xts.servicetests.test.ba.SingleParticipantCompletionParticipantCloseTest : close failure -- 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
15
0 / 0

[JBoss JIRA] (JBTM-1017) BASubordinateCrashDuringComplete.txt byteman rule causes a NPE exception to be thrown

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1017: ----------------------------------- Summary: BASubordinateCrashDuringComplete.txt byteman rule causes a NPE exception to be thrown Key: JBTM-1017 URL: https://issues.jboss.org/browse/JBTM-1017 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.1, 5.0.0.M2 Comment by Amos, which was correct: {quote} For tracing SubordinateCoordinatorCompletionParticipantStub compensate throw exceptions, there are 3 rules in BASubordinateCrashDuringComplete script. RULE trace subordinate participant stub compensate with no coordinator CLASS com.arjuna.wst11.stub.SubordinateCoordinatorCompletionParticipantStub METHOD compensate AT THROW 3 ... RULE trace subordinate participant stub compensate with unactivated coordinator CLASS com.arjuna.wst11.stub.SubordinateCoordinatorCompletionParticipantStub METHOD compensate AT THROW 4 ... RULE trace subordinate participant stub compensate with system exception from coordinator CLASS com.arjuna.wst11.stub.SubordinateCoordinatorCompletionParticipantStub METHOD compensate AT THROW 5 ... for SubordinateCoordinatorCompletionParticipantStub.java public void compensate() throws FaultedException, WrongStateException, SystemException {...} I read from byteman document which has the following describes about AT THROW: An AT THROW specifier identifies a throw operation within the trigger method as the trigger point. The throw operation may be qualified by a, possibly package-qualified, typename identifying the lexical type of the thrown exception. If a count N is supplied then the location specifies the Nth textual occurrence of a throw. If the keyword ALL is specified in place of a count then the rule will be triggered at all matching occurrences of a throw. I'm not sure about the textual occurrence of a throw. For this compensate method, AT THROW 3 => FaultedException AT THROW 4 => WrongStateException AT THROW 5 => SystemException is it right ? but the last throw rule causes NPE when the first booting jboss to run the test. I try to changes every AT THROW rule reducing one occurrence, and the test works fine. {quote} -- 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-1018) BACrashDuringCommit.txt byteman script does not detect CoordinatorCompletionCoordinatorEngine#closed

by Paul Robinson (JIRA)

Paul Robinson created JBTM-1018: ----------------------------------- Summary: BACrashDuringCommit.txt byteman script does not detect CoordinatorCompletionCoordinatorEngine#closed Key: JBTM-1018 URL: https://issues.jboss.org/browse/JBTM-1018 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.16.1, 5.0.0.M2 The was because the rule needs to run during recovery and it was set to run "IF NOT recovered" -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues July 2012