November 2011 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-984) Support @Recover and @RecoverComplete annotations in the TXFramework

by Paul Robinson (Created) (JIRA)

Support @Recover and @RecoverComplete annotations in the TXFramework -------------------------------------------------------------------- Key: JBTM-984 URL: https://issues.jboss.org/browse/JBTM-984 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 A simple test should be able to check this. -- 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

13 years

2
3
0 / 0

[JBoss JIRA] (JBTM-973) Allow a Client to remote WS be a lifecycle handler

by Paul Robinson (Created) (JIRA)

Allow a Client to remote WS be a lifecycle handler -------------------------------------------------- Key: JBTM-973 URL: https://issues.jboss.org/browse/JBTM-973 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: TxBridge Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.M2 This method can be called from a web service method while a transaction is active to notify the framework that no changes have been made during execution of the service method. This is a useful alternative to annotating the ServiceRequest as ReadOnly as it allows the business logic to decide at runtime if modifications were made. {code} public interface Control { public void readOnly(); } {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

13 years

2
4
0 / 0

[JBoss JIRA] (JBTM-951) Extend XTS crash recovery suite

by Paul Robinson (Created) (JIRA)

Extend XTS crash recovery suite ------------------------------- Key: JBTM-951 URL: https://issues.jboss.org/browse/JBTM-951 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Once we have code coverage in place we can then spot areas in need of greater coverage. -- 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

13 years

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-912) jbossts-xts-testsuite-eap5.1.x-ci fails due to "cannot find symbol: AddressingProperties"

by Paul Robinson (JIRA)

jbossts-xts-testsuite-eap5.1.x-ci fails due to "cannot find symbol: AddressingProperties" ----------------------------------------------------------------------------------------- Key: JBTM-912 URL: https://issues.jboss.org/browse/JBTM-912 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.6.1.CP13 See https://hudson.qa.jboss.com/hudson/view/JBossTS/job/jbossts-xts-testsuite... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
4
0 / 0

[JBoss JIRA] (JBTM-950) Improve XTS crash recvovery tests to use one server per participant

by Paul Robinson (Created) (JIRA)

Improve XTS crash recvovery tests to use one server per participant ------------------------------------------------------------------- Key: JBTM-950 URL: https://issues.jboss.org/browse/JBTM-950 Project: JBoss Transaction Manager Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 5.0.0.Final Currently the XTS crash recovery tests locates the client, coordinator and participants in the same server. This results in them all crashing and recovering at the same time. We should improve the tests to run one server each for the client, coordinator and each participant. -- 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

13 years

2
1
0 / 0

[JBoss JIRA] (JBTM-959) Some XTS services fail to deploy to AS7 when deploying from Arquillian based test

by Ivo Studensky (Created) (JIRA)

Some XTS services fail to deploy to AS7 when deploying from Arquillian based test --------------------------------------------------------------------------------- Key: JBTM-959 URL: https://issues.jboss.org/browse/JBTM-959 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: XTS Affects Versions: 4.15.3 Reporter: Ivo Studensky Assignee: Paul Robinson Some of the XTS services fail to deploy to AS7 when deploying by an Arquillian test within the AS7 testsuite. The org.jboss.as.webservices.publish.EndpointPublisherImpl.publish() method fails in org.apache.naming.resources.FileDirContext.setDocBase() method which gets an invalid path to the AS7 tmp directory in which the context path occurs twice, see the stacktrace below and take notice of 'target/xts/standalone/tmp' substring in it. This issue does not occur when the AS7 is manually started from the command line, but it only occurs when started by Arquillian from the new AS7 testsuite. However, it does not seem to hit all the XTS functionality as the wsas and wscf tests pass. Only ws-c, ws-t and ws-tx tests are hit by it. The stacktrace snippet from target/xts/standalone/logs/server.log: {noformat} 14:48:30,579 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-2) WSDL published to: file:/home/studensky/job/git/jboss-as/testsuite/integration/target/xts/standalone/data/wsdl/ws-t11-client.deployment/TerminationParticipantService.wsdl 14:48:30,585 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-7) Setting the server's publish address to be http://localhost:8080/ws-t11-participant/BusinessAgreementWithCoordinator... 14:48:30,597 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error starting static Resources: java.lang.IllegalArgumentException: Document base /home/studensky/job/git/jboss-as/testsuite/integration/target/xts/standalone/tmp/target/xts/standalone/tmp/ws-t11-client does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:148) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3554) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3723) [jbossweb-7.0.3.Final.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.webservices.publish.EndpointPublisherImpl.startWebApp(EndpointPublisherImpl.java:133) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:103) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:81) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:76) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.as.webservices.service.EndpointPublishService.start(EndpointPublishService.java:87) [jboss-as-webservices-server-integration-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29] at java.lang.Thread.run(Thread.java:662) [:1.6.0_29] 14:48:30,599 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error in resourceStart() 14:48:30,603 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/ws-t11-client] startup failed due to previous errors 14:48:30,603 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/ws-t11-client] has not been started {noformat} The list of services affected by this issue: /ws-t11-client /ws-t11-participant /ws-t11-coordinator /ws-c11 -- 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

13 years

7
20
0 / 0

[JBoss JIRA] (JBTM-958) jbossts-xts-testsuite-eap5.1.x-ci failing on QE Jenkins server

by Paul Robinson (Created) (JIRA)

jbossts-xts-testsuite-eap5.1.x-ci failing on QE Jenkins server -------------------------------------------------------------- Key: JBTM-958 URL: https://issues.jboss.org/browse/JBTM-958 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Paul Robinson Assignee: Paul Robinson Fix For: 4.6.1.CP13 AS failing to boot: {code} ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /mnt/hudson_workspace/workspace/jbossts-xts-testsuite-eap5.1.x-ci/jboss-as JAVA: /qa/tools/opt/jdk1.6.0_last/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true CLASSPATH: /mnt/hudson_workspace/workspace/jbossts-xts-testsuite-eap5.1.x-ci/jboss-as/bin/run.jar:/qa/tools/opt/jdk1.6.0_last/lib/tools.jar ========================================================================= Error occurred during initialization of VM Could not reserve enough space for object heap {code} I'm re-running to see if it passes on a different machine. I'll also investigate how to specify a machine with a minimum of 2GB ram. -- 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

13 years

7
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2011