From issues at jboss.org Fri May 1 04:07:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:07:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2383) Update standalone JCA quickstarts to use IronJacamar test runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2383: -------------------------------- Fix Version/s: 6.later (was: 5.next) > Update standalone JCA quickstarts to use IronJacamar test runner > ---------------------------------------------------------------- > > Key: JBTM-2383 > URL: https://issues.jboss.org/browse/JBTM-2383 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.later > > > See this post for the improvements in embedded IronJacamar container: https://groups.google.com/forum/#!topic/ironjacamar-developers/Pat7ixJuX6s -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:08:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:08:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2383) Update standalone JCA quickstarts to use IronJacamar test runner In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064558#comment-13064558 ] Tom Jenkinson commented on JBTM-2383: ------------------------------------- I spoke to Jesper and he suggested waiting for the beta release which is a way off yet > Update standalone JCA quickstarts to use IronJacamar test runner > ---------------------------------------------------------------- > > Key: JBTM-2383 > URL: https://issues.jboss.org/browse/JBTM-2383 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 6.later > > > See this post for the improvements in embedded IronJacamar container: https://groups.google.com/forum/#!topic/ironjacamar-developers/Pat7ixJuX6s -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:09:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:09:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2378) org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2378: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/831, https://github.com/jbosstm/jboss-as/pull/37 > org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2378 > URL: https://issues.jboss.org/browse/JBTM-2378 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > {code:xml} > > org.jboss.narayana.jts > narayana-jts-idlj > ${version.org.jboss.narayana} > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > org.jboss.logmanager > jboss-logmanager > > > org.hornetq > hornetq-core > > > jfree > jfreechart > > > jfree > jcommon > > > tanukisoft > wrapper > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:09:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:09:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2378) org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2378: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2378 > URL: https://issues.jboss.org/browse/JBTM-2378 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > {code:xml} > > org.jboss.narayana.jts > narayana-jts-idlj > ${version.org.jboss.narayana} > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > org.jboss.logmanager > jboss-logmanager > > > org.hornetq > hornetq-core > > > jfree > jfreechart > > > jfree > jcommon > > > tanukisoft > wrapper > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:09:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:09:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2384) WildFly fails to start on Sansa because of missing javax.servlet.ServletException class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064559#comment-13064559 ] Tom Jenkinson commented on JBTM-2384: ------------------------------------- Looks like it was fixed in wildfly so closing as out of date > WildFly fails to start on Sansa because of missing javax.servlet.ServletException class > --------------------------------------------------------------------------------------- > > Key: JBTM-2384 > URL: https://issues.jboss.org/browse/JBTM-2384 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > > {code} > [hudson at sansa wildfly-9.0.0.CR1-SNAPSHOT]$ ./bin/standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/ > JAVA: /usr/local/jdk1.8.0/jre/bin/java > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n > ========================================================================= > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > Listening for transport dt_socket at address: 8787 > 15:30:51,961 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 15:30:52,230 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 15:30:52,336 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) starting > 15:30:54,086 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.jaxrs > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1185) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:432) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:327) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:313) > at org.jboss.as.server.ServerService.boot(ServerService.java:381) > at org.jboss.as.server.ServerService.boot(ServerService.java:356) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107) > ... 12 more > Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at org.jboss.as.jaxrs.JaxrsDeploymentDefinition.registerOperations(JaxrsDeploymentDefinition.java:92) > at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:153) > at org.jboss.as.controller.extension.ExtensionRegistry$DeploymentManagementResourceRegistration.registerSubModel(ExtensionRegistry.java:863) > at org.jboss.as.controller.extension.ExtensionRegistry$SubsystemRegistrationImpl.registerDeploymentModel(ExtensionRegistry.java:674) > at org.jboss.as.jaxrs.JaxrsExtension.initialize(JaxrsExtension.java:89) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:104) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletException from [Module "org.jboss.as.jaxrs:main" from local module loader @33cb5951 (finder: local module finder @365c30cc (roots: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 14 more > 15:30:54,103 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 15:30:54,106 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > 15:30:54,140 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) stopped in 29ms > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:09:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:09:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2384) WildFly fails to start on Sansa because of missing javax.servlet.ServletException class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2384: -------------------------------- Fix Version/s: (was: 5.next) > WildFly fails to start on Sansa because of missing javax.servlet.ServletException class > --------------------------------------------------------------------------------------- > > Key: JBTM-2384 > URL: https://issues.jboss.org/browse/JBTM-2384 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > > {code} > [hudson at sansa wildfly-9.0.0.CR1-SNAPSHOT]$ ./bin/standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/ > JAVA: /usr/local/jdk1.8.0/jre/bin/java > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n > ========================================================================= > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > Listening for transport dt_socket at address: 8787 > 15:30:51,961 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 15:30:52,230 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 15:30:52,336 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) starting > 15:30:54,086 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.jaxrs > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1185) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:432) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:327) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:313) > at org.jboss.as.server.ServerService.boot(ServerService.java:381) > at org.jboss.as.server.ServerService.boot(ServerService.java:356) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107) > ... 12 more > Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at org.jboss.as.jaxrs.JaxrsDeploymentDefinition.registerOperations(JaxrsDeploymentDefinition.java:92) > at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:153) > at org.jboss.as.controller.extension.ExtensionRegistry$DeploymentManagementResourceRegistration.registerSubModel(ExtensionRegistry.java:863) > at org.jboss.as.controller.extension.ExtensionRegistry$SubsystemRegistrationImpl.registerDeploymentModel(ExtensionRegistry.java:674) > at org.jboss.as.jaxrs.JaxrsExtension.initialize(JaxrsExtension.java:89) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:104) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletException from [Module "org.jboss.as.jaxrs:main" from local module loader @33cb5951 (finder: local module finder @365c30cc (roots: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 14 more > 15:30:54,103 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 15:30:54,106 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > 15:30:54,140 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) stopped in 29ms > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:10:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:10:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2384) WildFly fails to start on Sansa because of missing javax.servlet.ServletException class In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2384. ------------------------------- Resolution: Out of Date > WildFly fails to start on Sansa because of missing javax.servlet.ServletException class > --------------------------------------------------------------------------------------- > > Key: JBTM-2384 > URL: https://issues.jboss.org/browse/JBTM-2384 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > > {code} > [hudson at sansa wildfly-9.0.0.CR1-SNAPSHOT]$ ./bin/standalone.sh > ========================================================================= > JBoss Bootstrap Environment > JBOSS_HOME: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/ > JAVA: /usr/local/jdk1.8.0/jre/bin/java > JAVA_OPTS: -server -XX:+UseCompressedOops -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n > ========================================================================= > Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 > Listening for transport dt_socket at address: 8787 > 15:30:51,961 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final > 15:30:52,230 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 15:30:52,336 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) starting > 15:30:54,086 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("parallel-extension-add") failed - address: ([]): java.lang.RuntimeException: WFLYCTL0079: Failed initializing module org.jboss.as.jaxrs > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:115) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:803) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:601) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:354) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:330) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1185) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:432) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:327) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:313) > at org.jboss.as.server.ServerService.boot(ServerService.java:381) > at org.jboss.as.server.ServerService.boot(ServerService.java:356) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:271) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:192) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:107) > ... 12 more > Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletException > at org.jboss.as.jaxrs.JaxrsDeploymentDefinition.registerOperations(JaxrsDeploymentDefinition.java:92) > at org.jboss.as.controller.registry.ConcreteResourceRegistration.registerSubModel(ConcreteResourceRegistration.java:153) > at org.jboss.as.controller.extension.ExtensionRegistry$DeploymentManagementResourceRegistration.registerSubModel(ExtensionRegistry.java:863) > at org.jboss.as.controller.extension.ExtensionRegistry$SubsystemRegistrationImpl.registerDeploymentModel(ExtensionRegistry.java:674) > at org.jboss.as.jaxrs.JaxrsExtension.initialize(JaxrsExtension.java:89) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:131) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:104) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:144) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:127) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletException from [Module "org.jboss.as.jaxrs:main" from local module loader @33cb5951 (finder: local module finder @365c30cc (roots: /home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/hudson/gytis/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 14 more > 15:30:54,103 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 15:30:54,106 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > 15:30:54,140 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta6) stopped in 29ms > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:52:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:52:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2296) Provide better way of distributing IOR to users In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2296: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Provide better way of distributing IOR to users > ----------------------------------------------- > > Key: JBTM-2296 > URL: https://issues.jboss.org/browse/JBTM-2296 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, JTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.later > > > Original JIRA shows I used github. Maybe that's fine. Maybe not. Consider other options (too, or instead). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:52:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:52:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2339) MongoDB extension for Compensations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2339: -------------------------------- Fix Version/s: 5.later (was: 5.next) > MongoDB extension for Compensations > ----------------------------------- > > Key: JBTM-2339 > URL: https://issues.jboss.org/browse/JBTM-2339 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:52:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:52:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2340: -------------------------------- Fix Version/s: 5.later (was: 5.next) > Implement POC of MongoDB extension > ---------------------------------- > > Key: JBTM-2340 > URL: https://issues.jboss.org/browse/JBTM-2340 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:52:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:52:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie CI test hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2265: -------------------------------- Fix Version/s: 5.later (was: 5.next) > BlackTie CI test hang > --------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.later > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 04:59:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 04:59:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2385) The new thread association listener does not handle the Arjuna behaviour that TM::resume(null) == TM::suspend for us In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2385: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > The new thread association listener does not handle the Arjuna behaviour that TM::resume(null) == TM::suspend for us > -------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2385 > URL: https://issues.jboss.org/browse/JBTM-2385 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.next > > > AtomicAction treats a null resume as a suspend. The code for the listener does not appear aware of this special behaviour. > PR to come shortly to help explain (including comment in AA so you can see where the behaviour is defined). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 05:00:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 05:00:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2379) investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064563#comment-13064563 ] Tom Jenkinson commented on JBTM-2379: ------------------------------------- Great, please can you let me know when the PR is merged so I can start the 5.1.1 release? > investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2379 > URL: https://issues.jboss.org/browse/JBTM-2379 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, TxBridge, XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code:xml} > > org.jboss.narayana.xts > jbossxts > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > org.hornetq > hornetq-core > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana.xts > jbossxts > api > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana > jbosstxbridge > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.jboss.narayana.xts > ws-c11 > > > org.jboss.narayana.jta > narayana-jta > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 05:02:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 05:02:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2380) rts requires exclusion of easily made "provided" dependencies when importing into WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2380: ----------------------------------- Assignee: Tom Jenkinson (was: Michael Musgrove) > rts requires exclusion of easily made "provided" dependencies when importing into WildFly > ----------------------------------------------------------------------------------------- > > Key: JBTM-2380 > URL: https://issues.jboss.org/browse/JBTM-2380 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, REST > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > For example, we are excluding restat-util but then including it. Strange. > {code:xml} > > org.jboss.narayana.rts > restat-integration > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-bridge > ${version.org.jboss.narayana} > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-api > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-util > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.resteasy > jaxrs-api > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 05:09:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 1 May 2015 05:09:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2379) investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2379: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2379 > URL: https://issues.jboss.org/browse/JBTM-2379 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, TxBridge, XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > {code:xml} > > org.jboss.narayana.xts > jbossxts > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > org.hornetq > hornetq-core > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana.xts > jbossxts > api > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana > jbosstxbridge > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.jboss.narayana.xts > ws-c11 > > > org.jboss.narayana.jta > narayana-jta > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 05:14:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 05:14:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2380) rts requires exclusion of easily made "provided" dependencies when importing into WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2380: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/jboss-as/pull/40, https://github.com/jbosstm/narayana/pull/836 > rts requires exclusion of easily made "provided" dependencies when importing into WildFly > ----------------------------------------------------------------------------------------- > > Key: JBTM-2380 > URL: https://issues.jboss.org/browse/JBTM-2380 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, REST > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > For example, we are excluding restat-util but then including it. Strange. > {code:xml} > > org.jboss.narayana.rts > restat-integration > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-bridge > ${version.org.jboss.narayana} > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-api > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-util > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.resteasy > jaxrs-api > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:19:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:19:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2380) rts requires exclusion of easily made "provided" dependencies when importing into WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2380: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > rts requires exclusion of easily made "provided" dependencies when importing into WildFly > ----------------------------------------------------------------------------------------- > > Key: JBTM-2380 > URL: https://issues.jboss.org/browse/JBTM-2380 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, REST > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.1 > > > For example, we are excluding restat-util but then including it. Strange. > {code:xml} > > org.jboss.narayana.rts > restat-integration > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-bridge > ${version.org.jboss.narayana} > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-api > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-util > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.resteasy > jaxrs-api > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2382) Fix TXFramework pom.xml to execute tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2382. ------------------------------- > Fix TXFramework pom.xml to execute tests > ---------------------------------------- > > Key: JBTM-2382 > URL: https://issues.jboss.org/browse/JBTM-2382 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2380) rts requires exclusion of easily made "provided" dependencies when importing into WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2380. ------------------------------- > rts requires exclusion of easily made "provided" dependencies when importing into WildFly > ----------------------------------------------------------------------------------------- > > Key: JBTM-2380 > URL: https://issues.jboss.org/browse/JBTM-2380 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, REST > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.1 > > > For example, we are excluding restat-util but then including it. Strange. > {code:xml} > > org.jboss.narayana.rts > restat-integration > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-bridge > ${version.org.jboss.narayana} > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-api > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.narayana.rts > restat-util > > > > > org.jboss.narayana.rts > restat-util > ${version.org.jboss.narayana} > > > log4j > log4j > > > org.jboss.resteasy > jaxrs-api > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2381) Enable XTS trace logging from narayana.sh In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2381. ------------------------------- > Enable XTS trace logging from narayana.sh > ----------------------------------------- > > Key: JBTM-2381 > URL: https://issues.jboss.org/browse/JBTM-2381 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.1.1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2378) org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2378. ------------------------------- > org.jboss.narayana.jts.narayana-jts-idlj has a lot of exclusions when importing into an app server like WildFly - presumably a result of the uber jar process > ------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2378 > URL: https://issues.jboss.org/browse/JBTM-2378 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.1 > > > {code:xml} > > org.jboss.narayana.jts > narayana-jts-idlj > ${version.org.jboss.narayana} > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > org.jboss.logmanager > jboss-logmanager > > > org.hornetq > hornetq-core > > > jfree > jfreechart > > > jfree > jcommon > > > tanukisoft > wrapper > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2379) investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2379. ------------------------------- > investigate why xts/txbridge have a lot of exclusions required when importing into the application server - these may not be avoidable as it is intended for deployment in multiple environments > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2379 > URL: https://issues.jboss.org/browse/JBTM-2379 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, TxBridge, XTS > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.1.1 > > > {code:xml} > > org.jboss.narayana.xts > jbossxts > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > org.hornetq > hornetq-core > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana.xts > jbossxts > api > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.hornetq > hornetq-core > > > org.jboss.narayana.arjunacore > arjunacore > > > org.jboss.byteman > byteman > > > org.jboss.byteman > byteman-submit > > > jfree > jfreechart > > > jfree > jcommon > > > org.jboss.spec.javax.servlet > jboss-servlet-api_3.0_spec > > > > > org.jboss.narayana > jbosstxbridge > ${version.org.jboss.narayana} > > > commons-httpclient > commons-httpclient > > > commons-logging > commons-logging > > > org.jboss.narayana.xts > ws-c11 > > > org.jboss.narayana.jta > narayana-jta > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2377) org.jboss.narayana.compensations||txframework require too many exclusion filters when integrated in WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2377. ------------------------------- > org.jboss.narayana.compensations||txframework require too many exclusion filters when integrated in WildFly > ----------------------------------------------------------------------------------------------------------- > > Key: JBTM-2377 > URL: https://issues.jboss.org/browse/JBTM-2377 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.1.1 > > > The same dependencies are required for TXF as compensations: > {code:xml} > > org.jboss.narayana.compensations > compensations > ${version.org.jboss.narayana} > > > junit > junit > > > org.jboss.narayana.rts > restat-util > > > org.jboss.arquillian.junit > arquillian-junit-container > > > org.hibernate.javax.persistence > hibernate-jpa-2.0-api > > > org.jboss.weld > weld-core > > > > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:35:47 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:35:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2385) The new thread association listener does not handle the Arjuna behaviour that TM::resume(null) == TM::suspend for us In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2385. ------------------------------- > The new thread association listener does not handle the Arjuna behaviour that TM::resume(null) == TM::suspend for us > -------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2385 > URL: https://issues.jboss.org/browse/JBTM-2385 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.1.1 > > > AtomicAction treats a null resume as a suspend. The code for the listener does not appear aware of this special behaviour. > PR to come shortly to help explain (including comment in AA so you can see where the behaviour is defined). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:49 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2343) Add a new Observer SPI for tracking transaction state association changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2343. ------------------------------- > Add a new Observer SPI for tracking transaction state association changes > ------------------------------------------------------------------------- > > Key: JBTM-2343 > URL: https://issues.jboss.org/browse/JBTM-2343 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > We need a new interface to enable users to track thread-to-transaction association changes. See related JBTM-2342 for details -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:49 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:49 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2321) apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2321. ------------------------------- > apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 not found during Blacktie build > ------------------------------------------------------------------------------------- > > Key: JBTM-2321 > URL: https://issues.jboss.org/browse/JBTM-2321 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Build System > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana-quickstarts/139 > {code} > [ERROR] Failed to execute goal on project blacktie-C: Could not resolve dependencies for project org.jboss.narayana.blacktie:blacktie-C:pom:5.0.5.Final-SNAPSHOT: Could not find artifact apache-log4cxx.contrib:log4cxx:jar:centos70x64:902683 in jbossThirdParty (https://repository.jboss.org/nexus/content/repositories/thirdparty-releases/) -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:50 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:50 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2330) Document the procedure to discover and resolve heuristically completed branches in Narayana In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2330. ------------------------------- > Document the procedure to discover and resolve heuristically completed branches in Narayana > ------------------------------------------------------------------------------------------- > > Key: JBTM-2330 > URL: https://issues.jboss.org/browse/JBTM-2330 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > Our documentation is not complete in this area. We need to describe how users can detect heuristically completed branches in the system. It would be useful to consider this in standalone and embedded wildfly modes. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:50 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:50 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2362) DistributedRecoveryIntegrationTestCase#testSecondServerFailureBeforeCommit failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2362. ------------------------------- > DistributedRecoveryIntegrationTestCase#testSecondServerFailureBeforeCommit failure > ---------------------------------------------------------------------------------- > > Key: JBTM-2362 > URL: https://issues.jboss.org/browse/JBTM-2362 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/PROFILE=MAIN,jdk=jdk7.latest,label=linux/797/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:50 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:50 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2308. ------------------------------- > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.1.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:51 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:51 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1572) a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-1572. ------------------------------- > a failure in the txfooapp quickstart does not return -1 so it appears to run even when it hasn't > ------------------------------------------------------------------------------------------------ > > Key: JBTM-1572 > URL: https://issues.jboss.org/browse/JBTM-1572 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.1.0 > > Attachments: client.valgrind, JBTM-1572.txt, JBTM-1572.zip, server.valgrind, windbg.out > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Note, it will definitely be worth doing this in a branch/pull as I suspect the database isn't running atm so that will need a kick too -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:51 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:51 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2141) Narayana WildFly branch pull request CI testing does not work In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2141. ------------------------------- > Narayana WildFly branch pull request CI testing does not work > ------------------------------------------------------------- > > Key: JBTM-2141 > URL: https://issues.jboss.org/browse/JBTM-2141 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Minor > Fix For: 5.1.0 > > > Firstly, poller does not pass the correct branch to build. > Secondly, if correct branch is passed, the testing job fails to rebase WildFly. > CI failure after wrong branch passed: http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-wildfly/195/console > CI failure after rebase failure: http://172.17.131.2/view/Narayana+BlackTie-pulls/job/btny-pulls-wildfly/194/consoleText -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:51 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:51 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2374) Blacktie XATIM TestConnection test hanging In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2374. ------------------------------- > Blacktie XATIM TestConnection test hanging > ------------------------------------------ > > Key: JBTM-2374 > URL: https://issues.jboss.org/browse/JBTM-2374 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/804/ > Stack dump: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/804/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el6/console > {code} > Running org.jboss.narayana.blacktie.jatmibroker.core.transport.hybrid.TestConnection > 18:35:21,173 INFO [org.codehaus.stomp.jms.StompConnect] (StompConnect Server Thread: tcp://127.0.0.1:61613) Looking up name: java:/ConnectionFactory in JNDI InitialContext for JMS ConnectionFactory > 18:35:21,177 INFO [org.codehaus.stomp.jms.StompConnect] (StompConnect Server Thread: tcp://127.0.0.1:61613) Looking up name: java:/JmsXA in JNDI InitialContext for JMS ConnectionFactory > 18:35:21,179 ERROR [org.codehaus.stomp.tcp.TcpTransportServer] (StompConnect Server Thread: tcp://127.0.0.1:61613) Received accept error: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA: javax.naming.NameNotFoundException: JmsXA -- service jboss.naming.context.java.JmsXA > at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at javax.naming.InitialContext.lookup(InitialContext.java:411) > at javax.naming.InitialContext.lookup(InitialContext.java:411) > at org.codehaus.stomp.jms.StompConnect.createXAConnectionFactory(StompConnect.java:195) > at org.codehaus.stomp.jms.StompConnect.getXAConnectionFactory(StompConnect.java:84) > at org.codehaus.stomp.jms.StompConnect.assignProtocolConverter(StompConnect.java:64) > at org.codehaus.stomp.tcp.TcpTransportServer.run(TcpTransportServer.java:82) > at java.lang.Thread.run(Thread.java:744) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2331) TransactionalDriver may leave a JDBC Connection associated after transaction termination In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2331. ------------------------------- > TransactionalDriver may leave a JDBC Connection associated after transaction termination > ---------------------------------------------------------------------------------------- > > Key: JBTM-2331 > URL: https://issues.jboss.org/browse/JBTM-2331 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > 1) Start a transaction; > 2) Obtain a connection via the TransactionalDriver > 3) End transaction > 4) start another transaction > 5) Call connection.isClosed() > this will produce the following exception because the transactional driver thinks the connection is still associated: > {code} > java.lang.RuntimeException: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:228) > at com.redhat.ceylon.common.tools.CeylonTool.run(CeylonTool.java:368) > at com.redhat.ceylon.common.tools.CeylonTool.execute(CeylonTool.java:305) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at com.redhat.ceylon.launcher.Launcher.runInJava7Checked(Launcher.java:113) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:40) > at com.redhat.ceylon.launcher.Launcher.run(Launcher.java:33) > at com.redhat.ceylon.launcher.Launcher.main(Launcher.java:26) > Caused by: java.sql.SQLException: ARJUNA017003: Checking transaction and found that this connection is already associated with a different transaction! Obtain a new connection for this transaction. > at com.arjuna.ats.internal.jdbc.ConnectionImple.checkTransaction(ConnectionImple.java:1078) > at com.arjuna.ats.internal.jdbc.ConnectionImple.isClosed(ConnectionImple.java:417) > at ceylon.dbc.ConnectionStatus.connection(ConnectionStatus.ceylon:22) > at ceylon.dbc.Sql.prepareStatement$priv$(Sql.ceylon:89) > at ceylon.dbc.Sql.access$100(Sql.ceylon:701) > at ceylon.dbc.Sql$Update.execute$canonical$(Sql.ceylon:346) > at ceylon.dbc.Sql$Update.execute(Sql.ceylon:343) > at example.ceylon.transaction.tm.runTx_.runTx(transaction.ceylon:199) > at example.ceylon.transaction.tm.run_.run(transaction.ceylon:225) > at example.ceylon.transaction.tm.run_.main(transaction.ceylon) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at ceylon.modules.api.runtime.SecurityActions.invokeRunInternal(SecurityActions.java:58) > at ceylon.modules.api.runtime.SecurityActions.invokeRun(SecurityActions.java:48) > at ceylon.modules.api.runtime.AbstractRuntime.invokeRun(AbstractRuntime.java:101) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:167) > at ceylon.modules.api.runtime.AbstractRuntime.execute(AbstractRuntime.java:151) > at ceylon.modules.Main.execute(Main.java:69) > at ceylon.modules.Main.main(Main.java:42) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.modules.Module.run(Module.java:312) > at org.jboss.modules.Main.main(Main.java:460) > at ceylon.modules.bootstrap.CeylonRunTool.run(CeylonRunTool.java:208) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2367) Move ClassLoadingUtil from core to common In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2367. ------------------------------- > Move ClassLoadingUtil from core to common > ----------------------------------------- > > Key: JBTM-2367 > URL: https://issues.jboss.org/browse/JBTM-2367 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Common > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.0 > > > It can be moved down the hierarchy to remove the need for orbportability to depend on arjunacore. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2316) Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2316. ------------------------------- > Add missing ArjunaJTS/jtax and ArjunaJTA/jdbc report to code-coverage > --------------------------------------------------------------------- > > Key: JBTM-2316 > URL: https://issues.jboss.org/browse/JBTM-2316 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > I can't see the transactional driver or JTAx stuff in the code-coverage report and I also don't think its worth aggregating in the performance test harness into the coverage numbers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2101) Blacktie integration CSTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2101. ------------------------------- > Blacktie integration CSTest hang > -------------------------------- > > Key: JBTM-2101 > URL: https://issues.jboss.org/browse/JBTM-2101 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.1.0 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/427/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux32el5 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2356) REST-AT recovery failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2356. ------------------------------- > REST-AT recovery failure > ------------------------ > > Key: JBTM-2356 > URL: https://issues.jboss.org/browse/JBTM-2356 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > See linked forum post: > Start two serves A and B with the coordinator running on A and a participant on server B. Crash server B just before commit. When server B comes back up the coordinator fails to recover the transaction and returns 404 when asked about the transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:52 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:52 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2349) CompensationContext is destroyed once the first handler is invoked In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2349. ------------------------------- > CompensationContext is destroyed once the first handler is invoked > ------------------------------------------------------------------ > > Key: JBTM-2349 > URL: https://issues.jboss.org/browse/JBTM-2349 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Critical > Fix For: 5.1.0 > > > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java#L95 > https://github.com/jbosstm/narayana/blob/master/compensations/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java#L118 > If there are two handlers (compensation or confirmation), which need to access the same compensation scoped object, only the first one will succeed. Once the first handler is invoked from the ParticipantImpl, CompensationScope is destroyed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:53 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:53 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2376) Quickstarts fail after SPI upgrade In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2376. ------------------------------- > Quickstarts fail after SPI upgrade > ---------------------------------- > > Key: JBTM-2376 > URL: https://issues.jboss.org/browse/JBTM-2376 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-quickstarts-windows2008-catelyn/777/console > I guess they need an update in their poms? -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:53 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:53 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2373) TransactionListenerRegistry class not found by jts integration module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2373. ------------------------------- > TransactionListenerRegistry class not found by jts integration module > --------------------------------------------------------------------- > > Key: JBTM-2373 > URL: https://issues.jboss.org/browse/JBTM-2373 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.1.0 > > > Fails in all CI jobs requiring WildFly > {code} > 08:58:20,744 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.2.Final > 08:58:20,973 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 08:58:21,048 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0049: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta4) starting > 08:58:22,073 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 16) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version! > 08:58:22,126 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 08:58:22,145 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.1.Final > 08:58:22,155 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.1.Final > 08:58:22,204 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem. > 08:58:22,208 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors > 08:58:22,232 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main] > 08:58:22,234 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem > 08:58:22,238 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem > 08:58:22,238 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2 > 08:58:22,241 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 08:58:22,246 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.8.Final > 08:58:22,264 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final) > 08:58:22,318 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 08:58:22,320 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.2.0.Beta10 starting > 08:58:22,321 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = h2 > 08:58:22,324 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.0.Beta10 starting > 08:58:22,332 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension > 08:58:22,415 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service > 08:58:22,418 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 08:58:22,552 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server. > 08:58:22,556 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/welcome-content > 08:58:22,628 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: Host default-host starting > 08:58:22,702 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 08:58:22,801 WARN [org.jboss.modules] (MSC service thread 1-1) Failed to define class com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate in Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base)): java.lang.LinkageError: Failed to link com/arjuna/ats/jbossatx/BaseTransactionManagerDelegate (Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:99) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/jboss/tm/listener/TransactionListenerRegistry > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > ... 26 more > Caused by: java.lang.ClassNotFoundException: org.jboss.tm.listener.TransactionListenerRegistry from [Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 30 more > 08:58:22,811 WARN [org.jboss.modules] (MSC service thread 1-1) Failed to define class com.arjuna.ats.jbossatx.jta.TransactionManagerDelegate in Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base)): java.lang.LinkageError: Failed to link com/arjuna/ats/jbossatx/BaseTransactionManagerDelegate (Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:99) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/jboss/tm/listener/TransactionListenerRegistry > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > ... 26 more > Caused by: java.lang.ClassNotFoundException: org.jboss.tm.listener.TransactionListenerRegistry from [Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 30 more > 08:58:22,818 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.txn.ArjunaTransactionManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.LinkageError: Failed to link com/arjuna/ats/jbossatx/BaseTransactionManagerDelegate (Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77) > at org.jboss.modules.Module.loadModuleClass(Module.java:560) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:99) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > ... 3 more > Caused by: java.lang.NoClassDefFoundError: org/jboss/tm/listener/TransactionListenerRegistry > at java.lang.ClassLoader.defineClass1(Native Method) > at java.lang.ClassLoader.defineClass(ClassLoader.java:800) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432) > ... 26 more > Caused by: java.lang.ClassNotFoundException: org.jboss.tm.listener.TransactionListenerRegistry from [Module "org.jboss.jts.integration:main" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130) > ... 30 more > 08:58:22,971 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/standalone/deployments > 08:58:23,073 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.CR1 > 08:58:23,101 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaTransactionManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: Failed to start service > Caused by: java.lang.LinkageError: Failed to link com/arjuna/ats/jbossatx/BaseTransactionManagerDelegate (Module \"org.jboss.jts.integration:main\" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))) > Caused by: java.lang.NoClassDefFoundError: org/jboss/tm/listener/TransactionListenerRegistry > Caused by: java.lang.ClassNotFoundException: org.jboss.tm.listener.TransactionListenerRegistry from [Module \"org.jboss.jts.integration:main\" from local module loader @3bb508b6 (finder: local module finder @6a4f0359 (roots: /home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules,/home/gytis/workspace/wildfly/build/target/wildfly-9.0.0.CR1-SNAPSHOT/modules/system/layers/base))]"}} > 08:58:23,180 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0186: Services which failed to start: service jboss.txn.ArjunaTransactionManager: org.jboss.msc.service.StartException in service jboss.txn.ArjunaTransactionManager: Failed to start service > 08:58:23,599 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 08:58:23,600 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 08:58:23,600 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.0.CR1-SNAPSHOT (WildFly Core 1.0.0.Beta4) started (with errors) in 3178ms - Started 170 of 375 services (28 services failed or missing dependencies, 210 services are lazy, passive or on-demand) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2346) CMRIntegrationTest deployment failed because of Weld In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2346. ------------------------------- > CMRIntegrationTest deployment failed because of Weld > ---------------------------------------------------- > > Key: JBTM-2346 > URL: https://issues.jboss.org/browse/JBTM-2346 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/758/PROFILE=MAIN,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.077 sec <<< FAILURE! > com.hp.mwtests.ts.jta.commitmarkable.integration.CMRIntegrationTest Time elapsed: 16.075 sec <<< ERROR! > org.jboss.arquillian.container.spi.client.container.DeploymentException: Cannot deploy: test.war > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getActionResult(ServerDeploymentPlanResultFuture.java:134) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.getResultFromNode(ServerDeploymentPlanResultFuture.java:123) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:85) > at org.jboss.as.controller.client.helpers.standalone.impl.ServerDeploymentPlanResultFuture.get(ServerDeploymentPlanResultFuture.java:42) > at org.jboss.as.controller.client.helpers.standalone.ServerDeploymentHelper.deploy(ServerDeploymentHelper.java:55) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:77) > at org.jboss.as.arquillian.container.ArchiveDeployer.deployInternal(ArchiveDeployer.java:64) > at org.jboss.as.arquillian.container.ArchiveDeployer.deploy(ArchiveDeployer.java:46) > at org.jboss.as.arquillian.container.CommonDeployableContainer.deploy(CommonDeployableContainer.java:146) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:161) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$3.call(ContainerDeployController.java:128) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.executeOperation(ContainerDeployController.java:271) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deploy(ContainerDeployController.java:127) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.impl.client.container.DeploymentExceptionHandler.verifyExpectedExceptionDuringDeploy(DeploymentExceptionHandler.java:50) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createDeploymentContext(ContainerDeploymentContextHandler.java:78) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:95) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController$1.perform(ContainerDeployController.java:80) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachDeployment(ContainerDeployController.java:263) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.forEachManagedDeployment(ContainerDeployController.java:239) > at org.jboss.arquillian.container.impl.client.container.ContainerDeployController.deployManaged(ContainerDeployController.java:79) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.execute(ContainerEventController.java:101) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:84) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95) > {code} > {code} > Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > WARNING: Bundles path is deprecated and no longer used. > Feb 24, 2015 6:54:39 PM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal > INFO: Starting container with: [/usr/local/jdk1.7.0_51/bin/java, -D[Standalone], -Xms64m, -Xmx512m, -XX:MaxPermSize=512m, -Djava.net.preferIPv4Stack=true, -server, -Xmx1024m, -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n, -ea, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.modules.system.pkgs=org.jboss.byteman, -Dorg.jboss.boot.log.file=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log/server.log, -Dlogging.configuration=file:/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration/logging.properties, -jar, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/jboss-modules.jar, -mp, /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/modules, org.jboss.as.standalone, -Djboss.home.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT, -Djboss.server.base.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone, -Djboss.server.log.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/log, -Djboss.server.config.dir=/home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/configuration, -c=standalone-cmr.xml] > Listening for transport dt_socket at address: 8787 > 18:54:40,441 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.1.Final > 18:54:41,291 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.4.Final > 18:54:41,487 WARN [org.jboss.as.warn.fd-limit] (main) WFLYSRV0071: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended > 18:54:41,567 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) starting > 18:54:44,597 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute enabled is deprecated, and it might be removed in future version! > 18:54:44,837 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http) > 18:54:44,867 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final > 18:54:44,886 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final > 18:54:44,928 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.7.Final > 18:54:45,053 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 37) WFLYCLINF0001: Activating Infinispan subsystem. > 18:54:45,135 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 45) WFLYNAM0001: Activating Naming Subsystem > 18:54:45,130 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 43) WFLYJSF0007: Activated the following JSF Implementations: [main] > 18:54:45,226 INFO [org.jboss.as.security] (ServerService Thread Pool -- 51) WFLYSEC0002: Activating Security Subsystem > 18:54:45,281 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service > 18:54:45,296 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 32) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 18:54:45,214 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 52) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique. > 18:54:45,957 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 36) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors > 18:54:46,288 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) WFLYWS0002: Activating WebServices Extension > 18:54:46,312 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.2.Final) > 18:54:46,577 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.0.Beta2 > 18:54:46,600 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2 > 18:54:46,610 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] > 18:54:48,054 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS] > 18:54:48,063 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.2.0.Beta8 starting > 18:54:48,065 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0003: Undertow 1.2.0.Beta8 starting > 18:54:48,112 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server. > 18:54:48,170 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080 > 18:54:48,172 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) WFLYUT0014: Creating file handler for path /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/welcome-content > 18:54:48,183 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting > 18:54:48,733 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Beta3 > 18:54:49,074 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/deployments > 18:54:49,766 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management > 18:54:49,766 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990 > 18:54:49,767 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) started in 10128ms - Started 203 of 380 services (210 services are lazy, passive or on-demand) > 18:54:50,870 INFO [org.jboss.as.repository] (management-handler-thread - 4) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/MAIN/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha2-SNAPSHOT/standalone/data/content/be/d1c9cd47a4d9b1119731defb4991fec5b863c8/content > 18:54:50,895 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:54:51,851 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:54:51,852 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jboss-transaction-spi:main") which may be changed or removed in future versions without notice. > 18:54:51,905 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment test.war > 18:54:51,995 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final > 18:54:52,703 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:54:52,748 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.9 (Final) > 18:54:52,868 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:54:54,097 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."test.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".WeldStartService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.4.Final.jar:1.2.4.Final] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51] > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > javax.enterprise.event.ObserverException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79) > at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of ) previously initiated loading for a different type with name "javax/sql/PooledConnection" > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) > at java.lang.Class.privateGetPublicMethods(Class.java:2651) > at java.lang.Class.privateGetPublicMethods(Class.java:2661) > at java.lang.Class.getMethods(Class.java:1467) > at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39) > at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63) > at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85) > at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89) > ... 26 more > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) > at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.4.Final.jar:1.2.4.Final] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.4.Final.jar:1.2.4.Final] > ... 3 more > 18:54:54,181 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "test.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > javax.enterprise.event.ObserverException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79) > at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of ) previously initiated loading for a different type with name \"javax/sql/PooledConnection\" > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) > at java.lang.Class.privateGetPublicMethods(Class.java:2651) > at java.lang.Class.privateGetPublicMethods(Class.java:2661) > at java.lang.Class.getMethods(Class.java:1467) > at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39) > at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63) > at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85) > at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89) > ... 26 more > "}} > 18:54:54,191 ERROR [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0021: Deploy of deployment "test.war" was rolled back with the following failure message: > {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"test.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"test.war\".WeldStartService: Failed to start service > Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions: > Exception 0 : > javax.enterprise.event.ObserverException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > at java.lang.Class.newInstance(Class.java:374) > at org.jboss.weld.security.NewInstanceAction.run(NewInstanceAction.java:33) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:40) > at org.jboss.weld.injection.Exceptions.rethrowException(Exceptions.java:78) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:97) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:79) > at org.jboss.weld.injection.ObserverMethodInvocationStrategy$2.notify(ObserverMethodInvocationStrategy.java:89) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:299) > at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:121) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:284) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:262) > at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:217) > at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:204) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:120) > at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:114) > at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:54) > at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:42) > at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) > at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:249) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:138) > at org.jboss.weld.bootstrap.AbstractBeanDeployer.fireBeanEvents(AbstractBeanDeployer.java:128) > at org.jboss.weld.bootstrap.BeanDeployer.deploy(BeanDeployer.java:322) > at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:273) > at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:406) > at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:83) > at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:93) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.LinkageError: loader constraint violation: loader (instance of ) previously initiated loading for a different type with name \"javax/sql/PooledConnection\" > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2531) > at java.lang.Class.privateGetPublicMethods(Class.java:2651) > at java.lang.Class.privateGetPublicMethods(Class.java:2661) > at java.lang.Class.getMethods(Class.java:1467) > at org.jboss.resteasy.cdi.Utils.isJaxrsAnnotatedClass(Utils.java:39) > at org.jboss.resteasy.cdi.Utils.isJaxrsResource(Utils.java:63) > at org.jboss.resteasy.cdi.Utils.isJaxrsComponent(Utils.java:85) > at org.jboss.resteasy.cdi.ResteasyCdiExtension.observeInjectionTarget(ResteasyCdiExtension.java:169) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:89) > ... 26 more > "}} > 18:54:54,221 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:54:54,294 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 91ms > 18:54:54,298 INFO [org.jboss.as.controller] (management-handler-thread - 4) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.deployment.unit."test.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 7 more ] > service jboss.deployment.unit."test.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, WFLYCTL0208: ... and 6 more ] > service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."com.sun.faces.config.ConfigureListener".START] > service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START] > service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] > service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START] > service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START] > service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService, service jboss.undertow.deployment.default-server.default-host./test, service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldTerminalListener".START] > service jboss.deployment.unit."test.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] > service jboss.deployment.unit."test.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."test.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."test.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."test.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."test.war".component."org.jboss.arquillian.protocol.servlet.runner.ServletTestRunner".START, WFLYCTL0208: ... and 4 more ] > service jboss.server.global-request-controller.control-point."test.war".undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] > service jboss.undertow.deployment.default-server.default-host./test (missing) dependents: [service jboss.deployment.unit."test.war".deploymentCompleteService] > service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test] > service jboss.undertow.deployment.default-server.default-host./test.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] > service jboss.undertow.deployment.default-server.default-host./test.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./test.UndertowDeploymentInfoService] > WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."test.war".WeldStartService > 18:54:54,377 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0211: Suspending server > 18:54:54,390 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested. > 18:54:54,398 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 18:54:54,406 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: Host default-host stopping > 18:54:54,480 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 18:54:54,501 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending > 18:54:54,501 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to /127.0.0.1:8080 > 18:54:54,797 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.2.0.Beta8 stopping > 18:54:54,865 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: WildFly Full 9.0.0.Alpha2-SNAPSHOT (WildFly Core 1.0.0.Alpha19) stopped in 423ms >  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2325) Allow the user to provide a reference to an XADataSource for Transactional Driver In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2325. ------------------------------- > Allow the user to provide a reference to an XADataSource for Transactional Driver > --------------------------------------------------------------------------------- > > Key: JBTM-2325 > URL: https://issues.jboss.org/browse/JBTM-2325 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.1.0 > > > Certain environments have class loader constraints that do not let the direct recoverable connection load the users configured XADataSource. It is therefore necessary to provide an implementation that can be passed by reference. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2368) CSV JMH benchmark file contains an unexpected double value In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2368. ------------------------------- > CSV JMH benchmark file contains an unexpected double value > ---------------------------------------------------------- > > Key: JBTM-2368 > URL: https://issues.jboss.org/browse/JBTM-2368 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > On one of the PERF axis CI runs a JMH benchmark csv file contained a double value in the "number of samples" column. The code in io.narayana.perf.jmh.BMParser expects an integer so fails with NumberFormatException (see linked CI job) > I don't know why JMH would use a double here (since in all other perf runs for the same benchmark it has used an integer). Anyway, I think I will just update the parser to accept a double or an int for this column. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2090) BlackTie process terminating with default action of signal 13 (SIGPIPE) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2090. ------------------------------- > BlackTie process terminating with default action of signal 13 (SIGPIPE) > ----------------------------------------------------------------------- > > Key: JBTM-2090 > URL: https://issues.jboss.org/browse/JBTM-2090 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Labels: linux64el6, linux64el7 > Fix For: 5.1.0 > > > http://172.17.131.2/view/Narayana+BlackTie/job/narayana/419/PROFILE=BLACKTIE,jdk=jdk7.latest,label=linux64el6/artifact/blacktie/xatmi/target/cpp-test-classes/blacktie-xatmi-valgrind.log > {code} > ==11776== Process terminating with default action of signal 13 (SIGPIPE) > ==11776== at 0x72734ED: ??? (in /lib64/libpthread-2.12.so) > ==11776== by 0x4E4C136: apr_socket_send (in /usr/lib64/libapr-1.so.0.3.9) > ==11776== by 0x54F05CB: HybridSocketEndpointQueue::_send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:305) > ==11776== by 0x54F081F: HybridSocketEndpointQueue::send(char const*, long, long, char*, int, long, long, char const*, char const*) (HybridSocketEndpointQueue.cxx:347) > ==11776== by 0x54EB35C: HybridSocketSessionImpl::send(message_t&) (HybridSocketSessionImpl.cxx:536) > ==11776== by 0x6D1894D: send(Session*, char const*, char*, long, int, long, long, message_t&, long, int, long, bool, char*) (XATMIc.cxx:147) > ==11776== by 0x6D18D4F: send(Session*, char const*, char*, long, int, long, long, long, int, long, bool, char*) (XATMIc.cxx:183) > ==11776== by 0x6D24122: tpdiscon (XATMIc.cxx:1220) > ==11776== by 0x497211: TestTPConnect::tearDown() (TestTPConnect.cxx:66) > ==11776== by 0x49B74A: CppUnit::TestCaller::tearDown() (TestCaller.h:182) > ==11776== by 0x3707A29B36: CppUnit::TestCaseMethodFunctor::operator()() const (TestCase.cpp:32) > ==11776== by 0x3707A1BEA3: CppUnit::DefaultProtector::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (DefaultProtector.cpp:15) > ==11776== by 0x3707A25C18: CppUnit::ProtectorChain::ProtectFunctor::operator()() const (ProtectorChain.cpp:20) > ==11776== by 0x3707A2595B: CppUnit::ProtectorChain::protect(CppUnit::Functor const&, CppUnit::ProtectorContext const&) (ProtectorChain.cpp:77) > ==11776== by 0x3707A3164F: CppUnit::TestResult::protect(CppUnit::Functor const&, CppUnit::Test*, std::string const&) (TestResult.cpp:178) > ==11776== by 0x3707A2989B: CppUnit::TestCase::run(CppUnit::TestResult*) (TestCase.cpp:97) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A2A10B: CppUnit::TestComposite::doRunChildTests(CppUnit::TestResult*) (TestComposite.cpp:64) > ==11776== by 0x3707A2A035: CppUnit::TestComposite::run(CppUnit::TestResult*) (TestComposite.cpp:23) > ==11776== by 0x3707A31429: CppUnit::TestResult::runTest(CppUnit::Test*) (TestResult.cpp:145) > ==11776== by 0x3707A33A21: CppUnit::TestRunner::run(CppUnit::TestResult&, std::string const&) (TestRunner.cpp:96) > ==11776== by 0x3707A369CA: CppUnit::TextTestRunner::run(std::string, bool, bool, bool) (TextTestRunner.cpp:64) > ==11776== by 0x4F6F83: main (TestRunner.cxx:27) > --11776-- Discarding syms at 0x973f480-0x973fec8 in /usr/lib64/gconv/ISO8859-1.so due to munmap() > --11776-- Discarding syms at 0x953b580-0x953ccd8 in /usr/lib64/gconv/UTF-16.so due to munmap() > --11776-- Discarding syms at 0xc9461f0-0xc94e648 in /lib64/libnss_files-2.12.so due to munmap() > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2341) Add two more statistics In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2341. ------------------------------- > Add two more statistics > ----------------------- > > Key: JBTM-2341 > URL: https://issues.jboss.org/browse/JBTM-2341 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > Add the following two statistics: > System Rollbacks (the number of transactions that were rolled back due to an internal system error such as failure to write a log); > Average Commit Time. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-860) use XAResourceWrapper metadata for assume complete In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-860. ------------------------------ > use XAResourceWrapper metadata for assume complete > -------------------------------------------------- > > Key: JBTM-860 > URL: https://issues.jboss.org/browse/JBTM-860 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Resource Manager > Affects Versions: 4.15.0 > Reporter: Jonathan Halliday > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > In the XA protocol a time window exists wherein the RM has committed and thus forgotten a tx branch but the TM has not yet deleted its log. A crash during this window currently results in an unrecoverable situation, as the TM assumes the branch belongs to an RM that is uncontactable and will retry recovery indefinitely. This stems from an inability to relate the Xid to a specific RM. It can be overridden globally with JTAEnvironmentBean.xaAssumeRecoveryComplete, but we would prefer more fine-grained control. With the availability of RM id information from XAResourceWrapper this becomes feasible. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:54 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:54 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2336) Transactional Driver tests fail on MySQL and Postgres database In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2336. ------------------------------- > Transactional Driver tests fail on MySQL and Postgres database > -------------------------------------------------------------- > > Key: JBTM-2336 > URL: https://issues.jboss.org/browse/JBTM-2336 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Tom Jenkinson > Priority: Blocker > Labels: Regression > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/736/PROFILE=QA_JTA,jdk=jdk7.latest,label=linux -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2355) Upgrade Narayana to use Wildfly 9.0.0.CR1-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2355. ------------------------------- > Upgrade Narayana to use Wildfly 9.0.0.CR1-SNAPSHOT > -------------------------------------------------- > > Key: JBTM-2355 > URL: https://issues.jboss.org/browse/JBTM-2355 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.1.0 > > > it has broken the narayana build > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/787/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2322) Add linux64el7 to the Narayana CI matrix for BlackTie In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2322. ------------------------------- > Add linux64el7 to the Narayana CI matrix for BlackTie > ----------------------------------------------------- > > Key: JBTM-2322 > URL: https://issues.jboss.org/browse/JBTM-2322 > Project: JBoss Transaction Manager > Issue Type: Task > Components: BlackTie > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.1.0 > > > Currently we do not build blacktie on the EL7 node (sansa). We should do this and add it to the narayana matrix job: http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2139) update the narayana-quickstart jobs to make sure the txfooapp example is working In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2139. ------------------------------- > update the narayana-quickstart jobs to make sure the txfooapp example is working > -------------------------------------------------------------------------------- > > Key: JBTM-2139 > URL: https://issues.jboss.org/browse/JBTM-2139 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: BlackTie, Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2327) wildfly-blacktie does not contain jars in the release In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2327. ------------------------------- > wildfly-blacktie does not contain jars in the release > ----------------------------------------------------- > > Key: JBTM-2327 > URL: https://issues.jboss.org/browse/JBTM-2327 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.4 > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.1.0 > > > it does not copy the artifact into the module folder as it looks like missing the "copy-module-artifacts="true" in the server-provisioning.xml -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2359) cersei needs libaio-devel installing, causes txfooapp quickstart failed with missing the libaio.so In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2359. ------------------------------- > cersei needs libaio-devel installing, causes txfooapp quickstart failed with missing the libaio.so > -------------------------------------------------------------------------------------------------- > > Key: JBTM-2359 > URL: https://issues.jboss.org/browse/JBTM-2359 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana+BlackTie/job/narayana-quickstarts/182/console > {noformat} > [exec] [cc] /usr/bin/ld: warning: libaio.so.1, needed by instantclient_11_2/lib/libclntsh.so, not found (try using -rpath or -rpath-link) > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] [cc] /usr/bin/ld: warning: libaio.so.1, needed by instantclient_11_2/lib/libclntsh.so, not found (try using -rpath or -rpath-link) > [exec] > [exec] BUILD SUCCESSFUL > [exec] Total time: 3 seconds > [exec] Checking for host: cersei.eng.hst.ams2.redhat.com or ip: 10.39.168.24 > [exec] ./server: error while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2301) PerformanceTest regression In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2301. ------------------------------- > PerformanceTest regression > -------------------------- > > Key: JBTM-2301 > URL: https://issues.jboss.org/browse/JBTM-2301 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/693/PROFILE=MAIN,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: io.narayana.perf.PerformanceTest > ------------------------------------------------------------------------------- > Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.898 sec <<< FAILURE! > regressionTest(io.narayana.perf.PerformanceTest) Time elapsed: 6.268 sec <<< FAILURE! > junit.framework.AssertionFailedError: There should have been a perf regression > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at io.narayana.perf.PerformanceTest.regressionTest(PerformanceTest.java:296) > {code} > {code} > Test Run: testTimeout (200 calls using 2 threads) > ExecutionException exception: java.util.concurrent.BrokenBarrierException > ExecutionException exception: java.util.concurrent.BrokenBarrierException > testTimeout: 0.000000 calls / second (200 calls in 0 ms using 2 threads. 201 errors) > Test Run: (100000 calls using 10 threads) > TestPerformance for 100000!: 17164.435290 calls / second (total time: 5826 ms versus 46786 ms) > Test Run: (1 calls using 1 threads) > testSingleCall!: 1000.000000 calls / second (1 calls in 1 ms using 1 threads. 0 errors) > Test Run: (10000 calls using 10 threads) > perfTest!: 4268.032437 calls / second (10000 calls in 2343 ms using 10 threads. 0 errors) > Test Run: (100 calls using 2 threads) > java.lang.RuntimeException: Testing throw exception > at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:412) > at io.narayana.perf.PerformanceTest$7.doWork(PerformanceTest.java:406) > at io.narayana.perf.Measurement$1.call(Measurement.java:339) > at io.narayana.perf.Measurement$1.call(Measurement.java:324) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > testCancelOnException!: 33333.333333 calls / second (100 calls in 3 ms using 2 threads. 20 errors) > Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) > Test Run: io.narayana.perf.PerformanceTest_regressionTest (10000 calls using 10 threads) > Test Run: (1000 calls using 10 threads) > testAbortMeasurement2: 0.000000 calls / second (1000 calls in 0 ms using 10 threads. 11 errors) > Test Warm Up: io.narayana.perf.PerformanceTest_readPerfArgsTest: (10 calls using 50 threads) > Test Run: io.narayana.perf.PerformanceTest_readPerfArgsTest (1000000 calls using 50 threads) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2337) Add a PR profile for triggering a performance check In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2337. ------------------------------- > Add a PR profile for triggering a performance check > --------------------------------------------------- > > Key: JBTM-2337 > URL: https://issues.jboss.org/browse/JBTM-2337 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > Add an extra profile to our build script (scripts/hudson/narayana.sh) to force a performance run on PRs that require a performance regression check. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2358) Benchmark the different Object Store Implementations In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2358. ------------------------------- > Benchmark the different Object Store Implementations > ---------------------------------------------------- > > Key: JBTM-2358 > URL: https://issues.jboss.org/browse/JBTM-2358 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > Include object store performance testing in the benchmark suite: > - Volatile > - File > - HornetQ store > - JDBC -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2361) Remove dependency on test-utils In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2361. ------------------------------- > Remove dependency on test-utils > ------------------------------- > > Key: JBTM-2361 > URL: https://issues.jboss.org/browse/JBTM-2361 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > The benchmark testsuite has a historical dependency on artifact org.jboss.narayana:test-utils which should now be removed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2323) Resume dualstack testing on the NCL CI cluster In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2323. ------------------------------- > Resume dualstack testing on the NCL CI cluster > ---------------------------------------------- > > Key: JBTM-2323 > URL: https://issues.jboss.org/browse/JBTM-2323 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > The new CI nodes are not configured for IPv6. As this is a bit specialised it would make sense to keep this job back on the Newcastle cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:55 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2354) PR Checker for narayana quickstarts broken In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2354. ------------------------------- > PR Checker for narayana quickstarts broken > ------------------------------------------ > > Key: JBTM-2354 > URL: https://issues.jboss.org/browse/JBTM-2354 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > The quickstart PR job btny-pulls-quickstart is reporting pass when the build has actually failed. Here is an example: > http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-quickstart/70 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2353) Compensation handler interceptors should not throw exception, if there is no transaction In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2353. ------------------------------- > Compensation handler interceptors should not throw exception, if there is no transaction > ---------------------------------------------------------------------------------------- > > Key: JBTM-2353 > URL: https://issues.jboss.org/browse/JBTM-2353 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.1.0 > > > @TXCompensate, @TXConfirm, and @TxLogged interceptors throw exception, if there is not transaction. However, transaction availability check is also done by @Compensatable interceptor. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2342) Add callbacks for thread-to-transaction association changes In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2342. ------------------------------- > Add callbacks for thread-to-transaction association changes > ----------------------------------------------------------- > > Key: JBTM-2342 > URL: https://issues.jboss.org/browse/JBTM-2342 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > This feature calls for a mechanism to avoid issues around concurrent access to a JPA EM if a transaction times out. Currently EM cleanup happens in AC callbacks - if those callbacks happen on the application thread there is no issue but if they happen on the reaper thread then it is possible for the EM to be manipulated whilst the application is still using it. > The linked forum thread came up with 4 proposals to handle the problem: > # Reaper marks transaction as set rollback only: this solution has potentially insurmountable issues (eg JVM1 -> JVM2, JVM1 crashes, txn never gets commit/rollback called on it). In addition it would need to be configurable - some users want the reaper to do the timely rollback; > # WildFly wraps the TM/TSR and coordinates the running of all Synchronization callbacks. This solution is complex and does the AS have sufficient knowledge to coordinate callbacks correctly. Option 4 below is similar but the decision about what to do and when to do it is left in the hands of the relevant callbacks where the knowlege resides; > # Start a discussion on the JPA expert group to get certain thread unsafe Synchronization JPA callbacks used by EE container/Persistence providers changed. This is an option for the future; > # Trigger callbacks when the transaction is disassociated from a thread. For example, detaching any loaded entities and closing the EM can be done when all relevant callbacks, namely the afterCompletion callback (triggered on the reaper thread) and the txn disassociated callback (triggered on the application thread) have been seen. > This JIRA will implement option 4. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2333) Blacktie subsystem build fails, because of missing org.jacorb module In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2333. ------------------------------- > Blacktie subsystem build fails, because of missing org.jacorb module > -------------------------------------------------------------------- > > Key: JBTM-2333 > URL: https://issues.jboss.org/browse/JBTM-2333 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration, BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/731/ > {code} > [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build (feature-pack-build) on project wildfly-blacktie-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.0.0.Alpha8:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack > [ERROR] Missing module ModuleIdentifier{name='org.jacorb', slot='main'}. Module was required by [ModuleIdentifier{name='org.wildfly.extension.blacktie', slot='main'}] > [ERROR] -> [Help 1] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2371) Error while creating coverage report In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2371. ------------------------------- > Error while creating coverage report > ------------------------------------ > > Key: JBTM-2371 > URL: https://issues.jboss.org/browse/JBTM-2371 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/185/console > [jacoco:report] Loading execution data file /home/hudson/workspace/narayana-codeCoverage/qa/testoutput/jacoco-qa.exec > BUILD FAILED > /home/hudson/workspace/narayana-codeCoverage/qa/run-tests.xml:544: Error while creating report -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2363) Blacktie c++ tx client build build failure In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2363. ------------------------------- > Blacktie c++ tx client build build failure > ------------------------------------------ > > Key: JBTM-2363 > URL: https://issues.jboss.org/browse/JBTM-2363 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.1.0 > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/797/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2350) CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2350. ------------------------------- > CDI Transactional interceptors are not thread safe. (previousUserTransactionAvailability) > ----------------------------------------------------------------------------------------- > > Key: JBTM-2350 > URL: https://issues.jboss.org/browse/JBTM-2350 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.0.0, 5.0.1, 5.0.2, 5.0.3, 5.0.4 > Environment: Wildfly 8.1.0, Wildfly 8.2.0, linux, OS X > Reporter: Tomasz Krakowiak > Assignee: Tomasz Krakowiak > Fix For: 5.1.0 > > > The problem is with availability of `UserTransaction`. > Availability of UserTransaction is stored in `ServerVMClientUserTransaction.isAvailables` which is `ThreadLocal`. > `TransactionalInterceptorRequired` when intercepting call, stores thread local value of `isAvailables` in `TransactionalInterceptorBase.previousUserTransactionAvailability` field of interceptor - which is of type boolean(not thread local). > Here's a story: > We have a bean - `beanA` - with single method annotated transactional - `beanA.transactional()`. > This method is being called from two threads, where: > - Thread 1 is participating in BMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is true. > - Thread 2 is participating in CMT, therefore it's `ServerVMClientUserTransaction.isAvailables` value is false. > Both threads call `beanA.transactional()` at the same time. > What may happen: > 1. Thread 1 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to true. > 2. Thread 2 - enters method `beanA.transactional()`. > Interceptor sets previousUserTransactionAvailability to false. > 3. Thread 1 - exits method `beanA.transactional()` > Interceptor restores thread local value of `isAvailables` to false (leaked value from thread 2!) -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 1 09:37:56 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 1 May 2015 09:37:56 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2347) Make JMH perf benchmark failure threshold configurable In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson closed JBTM-2347. ------------------------------- > Make JMH perf benchmark failure threshold configurable > ------------------------------------------------------ > > Key: JBTM-2347 > URL: https://issues.jboss.org/browse/JBTM-2347 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Affects Versions: 5.0.4 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.0 > > > The PERF profile for PR testing (added in JBTM-2337) fails a job if the performance of any test degrades by more than 10%. The threshold needs to be configurable. > Additionally change test com.hp.mwtests.ts.arjuna.performance.Performance1 so that it does at least some work (the test is so trivial that it's possibly prone to anomalous timings). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 05:17:46 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 4 May 2015 05:17:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2386) Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT In-Reply-To: References: Message-ID: Amos Feng created JBTM-2386: ------------------------------- Summary: Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT Key: JBTM-2386 URL: https://issues.jboss.org/browse/JBTM-2386 Project: JBoss Transaction Manager Issue Type: Task Components: Application Server Integration Reporter: Amos Feng Assignee: Amos Feng http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/818 http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/819 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 05:43:45 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 05:43:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2387) Async Abort In-Reply-To: References: Message-ID: Mark Little created JBTM-2387: --------------------------------- Summary: Async Abort Key: JBTM-2387 URL: https://issues.jboss.org/browse/JBTM-2387 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Transaction Core Affects Versions: 5.1.1 Reporter: Mark Little Assignee: Mark Little Async prepare and commit always made sense. Rollback was something we'd add when/if there was a good scenario. Vert.x may well be that scenario, though see linked issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 05:46:45 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 05:46:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2388) Async transaction API for STM In-Reply-To: References: Message-ID: Mark Little created JBTM-2388: --------------------------------- Summary: Async transaction API for STM Key: JBTM-2388 URL: https://issues.jboss.org/browse/JBTM-2388 Project: JBoss Transaction Manager Issue Type: Feature Request Components: STM Affects Versions: 5.1.0 Reporter: Mark Little Assignee: Mark Little Add async begin, commit, rollback options. May be more generally useful, e.g., Vert.x, but place within STM for now. Refactor later if needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 07:31:45 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 4 May 2015 07:31:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2386) Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2386: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/837 > Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2386 > URL: https://issues.jboss.org/browse/JBTM-2386 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/818 > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/819 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 07:44:46 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 07:44:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: Mark Little created JBTM-2389: --------------------------------- Summary: Periodic build error messages Key: JBTM-2389 URL: https://issues.jboss.org/browse/JBTM-2389 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.1.1 Environment: Mac OS 10.9.5 Java(TM) SE Runtime Environment (build 1.7.0_05-b05) Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) Reporter: Mark Little Assignee: Tom Jenkinson While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified And then ... Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! java.lang.OutOfMemoryError: Java heap space at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 07:45:46 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 07:45:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little updated JBTM-2389: ------------------------------ Description: While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified And then in separate build attempts ... Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! java.lang.OutOfMemoryError: Java heap space at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. was: While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified Error occurred during initialization of VM Too small initial heap for new size specified And then ... Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! java.lang.OutOfMemoryError: Java heap space at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 07:47:46 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 07:47:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064961#comment-13064961 ] Mark Little commented on JBTM-2389: ----------------------------------- For completeness, just got this: T E S T S ------------------------------------------------------- Running com.arjuna.common.tests.propertyservice.PropertiesFactoryTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.106 sec Error occurred during initialization of VM Too small initial heap Error occurred during initialization of VM Too small initial heap Results : Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Narayana: all ..................................... SUCCESS [0.847s] [INFO] Narayana: common .................................. FAILURE [0.779s] [INFO] Narayana: Test Utilities .......................... SKIPPED [INFO] Narayana: Arjunacore .............................. SKIPPED [INFO] Narayana: ArjunaCore arjuna ....................... SKIPPED [INFO] Narayana: ArjunaCore txoj ......................... SKIPPED [INFO] Narayana: STM ..................................... SKIPPED [INFO] ------------------------------------------------------------------------ > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 07:57:45 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 07:57:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064967#comment-13064967 ] Mark Little commented on JBTM-2389: ----------------------------------- It's possible this is an issue with my local environment. Since a reboot I've not seen the problems come back. But before closing the issue it'd be good if someone else could run many builds and see if the problem arises. > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 08:00:58 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 08:00:58 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2388) Async transaction API for STM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2388. ------------------------------- Resolution: Done > Async transaction API for STM > ----------------------------- > > Key: JBTM-2388 > URL: https://issues.jboss.org/browse/JBTM-2388 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.1.0 > Reporter: Mark Little > Assignee: Mark Little > > Add async begin, commit, rollback options. May be more generally useful, e.g., Vert.x, but place within STM for now. Refactor later if needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 08:00:58 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 4 May 2015 08:00:58 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2388) Async transaction API for STM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2388. ----------------------------- > Async transaction API for STM > ----------------------------- > > Key: JBTM-2388 > URL: https://issues.jboss.org/browse/JBTM-2388 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.1.0 > Reporter: Mark Little > Assignee: Mark Little > > Add async begin, commit, rollback options. May be more generally useful, e.g., Vert.x, but place within STM for now. Refactor later if needed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 16:10:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 May 2015 16:10:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065182#comment-13065182 ] Tom Jenkinson commented on JBTM-2389: ------------------------------------- Hi Mark, We haven't seen this issue in CI and we run many builds there. Thanks, Tom > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 16:26:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 May 2015 16:26:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2386) Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2386: -------------------------------- Fix Version/s: 5.next > Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2386 > URL: https://issues.jboss.org/browse/JBTM-2386 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/818 > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/819 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 4 16:26:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 4 May 2015 16:26:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2386) Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2386: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade the wildfly to 9.0.0.CR2-SNAPSHOT > ----------------------------------------- > > Key: JBTM-2386 > URL: https://issues.jboss.org/browse/JBTM-2386 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Application Server Integration > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/818 > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/819 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:08:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 05:08:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Fix Version/s: 5.next > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:10:47 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 05:10:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Fix Version/s: (was: 5.next) > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:12:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 05:12:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-1339. ---------------------------------- Resolution: Out of Date The associated WildFly jira is now closed (WFLY-1077 JDK ORB Subsystem) so this JIRA is now out of date > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:15:55 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 May 2015 05:15:55 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie J In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2265: ---------------------------- Summary: BlackTie J (was: BlackTie CI test hang) > BlackTie J > ---------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.later > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:16:45 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 May 2015 05:16:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie Jatmibroker TestTPConversation hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2265: ---------------------------- Summary: BlackTie Jatmibroker TestTPConversation hang (was: BlackTie J) > BlackTie Jatmibroker TestTPConversation hang > -------------------------------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.later > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:21:46 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 May 2015 05:21:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie Jatmibroker TestTPConversation hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065328#comment-13065328 ] Amos Feng commented on JBTM-2265: --------------------------------- It looks like a time issue and the root cause is that the StompManager.send() method is not thread safe. It could send the wrong messages and when receiving the disconnect message resp it hangs. > BlackTie Jatmibroker TestTPConversation hang > -------------------------------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.later > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 05:43:46 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Tue, 5 May 2015 05:43:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2265) BlackTie Jatmibroker TestTPConversation hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2265: ---------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/838 > BlackTie Jatmibroker TestTPConversation hang > -------------------------------------------- > > Key: JBTM-2265 > URL: https://issues.jboss.org/browse/JBTM-2265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Affects Versions: 5.0.3 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.later > > Attachments: blacktie.zip, jstack.27403, jstack.27697 > > > CI job http://172.17.131.2/view/Narayana+BlackTie/job/narayana-dualstack/193 is hanging with what looks like a stomp comms error -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 06:05:45 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 5 May 2015 06:05:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065345#comment-13065345 ] Mark Little commented on JBTM-2389: ----------------------------------- OK I'll close this for now but I still wonder if there's a Mac issue at heart here. > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 06:05:46 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 5 May 2015 06:05:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little resolved JBTM-2389. ------------------------------- Resolution: Cannot Reproduce Bug > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 06:05:46 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Tue, 5 May 2015 06:05:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2389. ----------------------------- > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 07:32:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 May 2015 07:32:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2389) Periodic build error messages In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065412#comment-13065412 ] Tom Jenkinson commented on JBTM-2389: ------------------------------------- We do have CI running for Mac too. Mac CI runs on every pull request (that has MAIN profile - so most PRs) and I believe it runs once a week on master. Its quite an old version of MacOS we have in the NCL cluster though so you are right that it could be something in MacOS that we can't detect on our nodes. > Periodic build error messages > ----------------------------- > > Key: JBTM-2389 > URL: https://issues.jboss.org/browse/JBTM-2389 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Environment: Mac OS 10.9.5 > Java(TM) SE Runtime Environment (build 1.7.0_05-b05) > Java HotSpot(TM) 64-Bit Server VM (build 23.1-b03, mixed mode) > Reporter: Mark Little > Assignee: Tom Jenkinson > > While building STM today I've seen the following build-time errors several times. Since I've not seen them at all before and it's been a few weeks since I last built the system, I wonder if these are known issues? > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 sec > Running com.hp.mwtests.ts.txoj.concurrencycontrol.LockConflictUnitTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.605 sec > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > Error occurred during initialization of VM > Too small initial heap for new size specified > And then in separate build attempts ... > Running com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.428 sec <<< FAILURE! > testStateMachine(com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest) Time elapsed: 0.372 sec <<< ERROR! > java.lang.OutOfMemoryError: Java heap space > at com.hp.mwtests.ts.arjuna.objectstore.JDBCStoreTest.testStateMachine(JDBCStoreTest.java:95) > Builds do complete most of the time, so retrying the build is an option. But it's inconvenient. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 07:34:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 5 May 2015 07:34:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065413#comment-13065413 ] Tom Jenkinson commented on JBTM-1339: ------------------------------------- Hi [~mmusgrov], I don't think we should close this one yet. Didn't we say you were going to try to move to using the fork from WFLY of the ORB: https://github.com/wildfly/wildfly/blob/master/iiop-openjdk/pom.xml#L79 org.jboss.openjdk-orb openjdk-orb > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 08:34:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 08:34:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-1339: ------------------------------------ Good catch - thanks > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 08:36:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 08:36:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Fix Version/s: 5.next > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 08:36:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 08:36:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Affects Version/s: 5.1.1 > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 09:51:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 09:51:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2390: -------------------------------------- Summary: port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark Key: JBTM-2390 URL: https://issues.jboss.org/browse/JBTM-2390 Project: JBoss Transaction Manager Issue Type: Task Reporter: Michael Musgrove Assignee: Michael Musgrove Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 09:52:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 5 May 2015 09:52:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2390: ----------------------------------- Fix Version/s: 5.later > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 5 11:28:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 5 May 2015 11:28:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2365: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana.io/pull/1 > Create feature choice helper on narayana.io > ------------------------------------------- > > Key: JBTM-2365 > URL: https://issues.jboss.org/browse/JBTM-2365 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too. > Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on. > Needs experimentation to see what will work best. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 03:09:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 03:09:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2391) Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2391: ----------------------------------- Summary: Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT Key: JBTM-2391 URL: https://issues.jboss.org/browse/JBTM-2391 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson 10.0.0.Alpha1-SNAPSHOT is master on WFLY now -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 03:10:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 03:10:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2391) Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2391: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/839 > Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT > ------------------------------------------------------------ > > Key: JBTM-2391 > URL: https://issues.jboss.org/browse/JBTM-2391 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > > 10.0.0.Alpha1-SNAPSHOT is master on WFLY now -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 05:35:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 05:35:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065722#comment-13065722 ] Gytis Trikleris commented on JBTM-2297: --------------------------------------- The new repo is here: https://github.com/jboss-dockerfiles/narayana > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:27:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 06:27:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2295: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-dockerfiles/narayana/pull/1 > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:32:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 06:32:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2297) Store docker image for service(s) in JBoss repo In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris resolved JBTM-2297. ----------------------------------- Resolution: Done Narayana docker repository was created under jboss-dockerfiles organization. All further Narayana related dockerfiles should be stored there. > Store docker image for service(s) in JBoss repo > ----------------------------------------------- > > Key: JBTM-2297 > URL: https://issues.jboss.org/browse/JBTM-2297 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, JTS, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > > We have a repo for JBoss project docker images. Store our final version (not POC version I created) there. Also see if this also suggests a way of distributing and storing the docker file to create it/them. I'm assuming we don't need to store this information within the Narayana repo, but perhaps we do and in which case we'll probably need a docker directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:35:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 06:35:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2295: ---------------------------------- Fix Version/s: 5.later > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:37:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 06:37:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2375) Upload IDL and WSDL files to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2375: ---------------------------------- Fix Version/s: 5.later > Upload IDL and WSDL files to the web page > ----------------------------------------- > > Key: JBTM-2375 > URL: https://issues.jboss.org/browse/JBTM-2375 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > Upload IDL and WSDL files to the web page, so that they would be easy to find. Also, update documentation to use the correct links. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:50:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 06:50:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2391) Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2391: -------------------------------- Fix Version/s: 5.next > Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT > ------------------------------------------------------------ > > Key: JBTM-2391 > URL: https://issues.jboss.org/browse/JBTM-2391 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > 10.0.0.Alpha1-SNAPSHOT is master on WFLY now -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 06:51:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 06:51:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2391) Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2391: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade version of WFLY in pom.xml to 10.0.0.Alpha1-SNAPSHOT > ------------------------------------------------------------ > > Key: JBTM-2391 > URL: https://issues.jboss.org/browse/JBTM-2391 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > 10.0.0.Alpha1-SNAPSHOT is master on WFLY now -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 09:05:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 09:05:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2375) Upload IDL and WSDL files to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2375: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana.io/pull/2 > Upload IDL and WSDL files to the web page > ----------------------------------------- > > Key: JBTM-2375 > URL: https://issues.jboss.org/browse/JBTM-2375 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > Upload IDL and WSDL files to the web page, so that they would be easy to find. Also, update documentation to use the correct links. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:10:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:10:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2213: ---------------------------------- Fix Version/s: 5.later > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:11:46 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:11:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2213: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/840 > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:14:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 10:14:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065846#comment-13065846 ] Tom Jenkinson commented on JBTM-2213: ------------------------------------- I think this should be 5.next version? > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:16:46 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:16:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065848#comment-13065848 ] Gytis Trikleris commented on JBTM-2213: --------------------------------------- That's what me and Mike where not sure about yesterday. So do I simply put all the stuff to 5.next which I'm working on? Or do I work on 5.later and then we move them to 5.next during the planning? > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:18:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 10:18:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065850#comment-13065850 ] Tom Jenkinson commented on JBTM-2213: ------------------------------------- Yeah, 5.next just stops me chasing around with the version number that might change. 5.later are issues that will be in 5 but not necessarily next version and can be brought forward to 5.next prior to release. > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:19:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:19:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065851#comment-13065851 ] Gytis Trikleris commented on JBTM-2213: --------------------------------------- OK, I'll move this to 5.next then. > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:21:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:21:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2213: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:26:46 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:26:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2214) Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2214: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/841 > Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2214 > URL: https://issues.jboss.org/browse/JBTM-2214 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > > If you run: > ./build.sh clean install -DskipTests | grep "com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithParticipantCompletionStub.java:[173,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/SubordinateCoordinatorCompletionParticipantStub.java:[260,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithCoordinatorCompletionStub.java:[207,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[64,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[59,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[62,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[60,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/FailureBusinessParticipant.java:[106,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/DemoBusinessParticipant.java:[100,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/webservices/bainterop/participant/ParticipantCompletionParticipantAdapter.java:[56,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/xtstest/src/org/jboss/jbossts/xts/servicetests/service/participant/ParticipantCompletionTestParticipant.java:[99,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java:[144,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/remote/RemoteParticipant.java:[81,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[113,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[116,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 10:27:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 10:27:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2214) Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2214: ---------------------------------- Fix Version/s: 5.next > Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2214 > URL: https://issues.jboss.org/browse/JBTM-2214 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithParticipantCompletionStub.java:[173,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/SubordinateCoordinatorCompletionParticipantStub.java:[260,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithCoordinatorCompletionStub.java:[207,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[64,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[59,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[62,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[60,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/FailureBusinessParticipant.java:[106,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/DemoBusinessParticipant.java:[100,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/webservices/bainterop/participant/ParticipantCompletionParticipantAdapter.java:[56,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/xtstest/src/org/jboss/jbossts/xts/servicetests/service/participant/ParticipantCompletionTestParticipant.java:[99,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java:[144,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/remote/RemoteParticipant.java:[81,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[113,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[116,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 11:40:46 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 11:40:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2375) Upload IDL and WSDL files to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2375: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Upload IDL and WSDL files to the web page > ----------------------------------------- > > Key: JBTM-2375 > URL: https://issues.jboss.org/browse/JBTM-2375 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Upload IDL and WSDL files to the web page, so that they would be easy to find. Also, update documentation to use the correct links. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 11:40:47 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 11:40:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2295: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Cloud, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 11:40:47 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 6 May 2015 11:40:47 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2365) Create feature choice helper on narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2365: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > Create feature choice helper on narayana.io > ------------------------------------------- > > Key: JBTM-2365 > URL: https://issues.jboss.org/browse/JBTM-2365 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > It would be useful to have something on our homepage that lists all the different transports we use and what features are available when you select each of those transport. Mainly all features are available which allows us to list those too. > Ideally in the future it might replace our current landing page so we should try to include all details from that too where possible - so you could include an axis that said "commercial support available" STM = No, XTS = yes and so on. > Needs experimentation to see what will work best. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 12:52:45 2015 From: issues at jboss.org (Mark S (JIRA)) Date: Wed, 6 May 2015 12:52:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: Mark S created JBTM-2392: ---------------------------- Summary: XA recovery exceptions Key: JBTM-2392 URL: https://issues.jboss.org/browse/JBTM-2392 Project: JBoss Transaction Manager Issue Type: Feature Request Environment: * wildfly-8.2.0.Final * Windows 7 * Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64) Feb 25 2011 13:56:11 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) * Both Microsoft JDBC Driver for SQL Server 4.0 and 4.1 Drivers Reporter: Mark S Assignee: Tom Jenkinson h3. Wildfly Exception Stack Trace of Issue: {code} 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] {code} h3. SQL Server Profiler Stack Trace of Issue: declare @p2 int set @p2=-3 declare @p3 nvarchar(max) set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' declare @p5 varbinary(max) set @p5=NULL exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output select @p2, @p3, @p5 Possible Related Issues: * https://issues.jboss.org/browse/JBTM-1433 * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 12:52:46 2015 From: issues at jboss.org (Mark S (JIRA)) Date: Wed, 6 May 2015 12:52:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark S updated JBTM-2392: ------------------------- Environment: * wildfly-8.2.0.Final * Windows 7 * Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64) Feb 25 2011 13:56:11 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) * Both Microsoft JDBC Driver for SQL Server 4.0 and 4.1 Drivers was: * wildfly-8.2.0.Final * Windows 7 * Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64) Feb 25 2011 13:56:11 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) * Both Microsoft JDBC Driver for SQL Server 4.0 and 4.1 Drivers > XA recovery exceptions > ---------------------- > > Key: JBTM-2392 > URL: https://issues.jboss.org/browse/JBTM-2392 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Environment: * wildfly-8.2.0.Final > * Windows 7 > * Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64) Feb 25 2011 13:56:11 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) > * Both Microsoft JDBC Driver for SQL Server 4.0 and 4.1 Drivers > Reporter: Mark S > Assignee: Tom Jenkinson > > h3. Wildfly Exception Stack Trace of Issue: > {code} > 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > {code} > h3. SQL Server Profiler Stack Trace of Issue: > declare @p2 int > set @p2=-3 > declare @p3 nvarchar(max) > set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' > declare @p5 varbinary(max) > set @p5=NULL > exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output > select @p2, @p3, @p5 > Possible Related Issues: > * https://issues.jboss.org/browse/JBTM-1433 > * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 12:53:45 2015 From: issues at jboss.org (Mark S (JIRA)) Date: Wed, 6 May 2015 12:53:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark S updated JBTM-2392: ------------------------- Environment: wildfly-8.2.0.Final + Windows 7 + Microsoft SQL Server 2008 (SP2) + Microsoft JDBC 4.0 and 4.1 Drivers (was: * wildfly-8.2.0.Final * Windows 7 * Microsoft SQL Server 2008 (SP2) - 10.0.4064.0 (X64) Feb 25 2011 13:56:11 Copyright (c) 1988-2008 Microsoft Corporation Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) * Both Microsoft JDBC Driver for SQL Server 4.0 and 4.1 Drivers) > XA recovery exceptions > ---------------------- > > Key: JBTM-2392 > URL: https://issues.jboss.org/browse/JBTM-2392 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Environment: wildfly-8.2.0.Final + Windows 7 + Microsoft SQL Server 2008 (SP2) + Microsoft JDBC 4.0 and 4.1 Drivers > Reporter: Mark S > Assignee: Tom Jenkinson > > h3. Wildfly Exception Stack Trace of Issue: > {code} > 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > {code} > h3. SQL Server Profiler Stack Trace of Issue: > declare @p2 int > set @p2=-3 > declare @p3 nvarchar(max) > set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' > declare @p5 varbinary(max) > set @p5=NULL > exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output > select @p2, @p3, @p5 > Possible Related Issues: > * https://issues.jboss.org/browse/JBTM-1433 > * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 12:54:45 2015 From: issues at jboss.org (Mark S (JIRA)) Date: Wed, 6 May 2015 12:54:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark S updated JBTM-2392: ------------------------- Description: h3. Wildfly Exception Stack Trace of Issue: {code} 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] {code} h3. SQL Server Profiler Stack Trace of Issue: declare @p2 int set @p2=-3 declare @p3 nvarchar(max) set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' declare @p5 varbinary(max) set @p5=NULL exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output select @p2, @p3, @p5 h3. Possible Related Issues: * https://issues.jboss.org/browse/JBTM-1433 * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings was: h3. Wildfly Exception Stack Trace of Issue: {code} 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] {code} h3. SQL Server Profiler Stack Trace of Issue: declare @p2 int set @p2=-3 declare @p3 nvarchar(max) set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' declare @p5 varbinary(max) set @p5=NULL exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output select @p2, @p3, @p5 Possible Related Issues: * https://issues.jboss.org/browse/JBTM-1433 * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings > XA recovery exceptions > ---------------------- > > Key: JBTM-2392 > URL: https://issues.jboss.org/browse/JBTM-2392 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Environment: wildfly-8.2.0.Final + Windows 7 + Microsoft SQL Server 2008 (SP2) + Microsoft JDBC 4.0 and 4.1 Drivers > Reporter: Mark S > Assignee: Tom Jenkinson > > h3. Wildfly Exception Stack Trace of Issue: > {code} > 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > {code} > h3. SQL Server Profiler Stack Trace of Issue: > declare @p2 int > set @p2=-3 > declare @p3 nvarchar(max) > set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' > declare @p5 varbinary(max) > set @p5=NULL > exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output > select @p2, @p3, @p5 > h3. Possible Related Issues: > * https://issues.jboss.org/browse/JBTM-1433 > * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 16:22:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 16:22:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066013#comment-13066013 ] Tom Jenkinson commented on JBTM-2392: ------------------------------------- Looks like a duplicate of JBTM-2216 to me. https://github.com/jbosstm/narayana/blame/master/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/recovery/arjunacore/XARecoveryModule.java Its fixed in WFLY master version (was fixed in Narayana 5.0.4 which should be in WFLY since 9.Beta1). > XA recovery exceptions > ---------------------- > > Key: JBTM-2392 > URL: https://issues.jboss.org/browse/JBTM-2392 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Environment: wildfly-8.2.0.Final + Windows 7 + Microsoft SQL Server 2008 (SP2) + Microsoft JDBC 4.0 and 4.1 Drivers > Reporter: Mark S > Assignee: Tom Jenkinson > > h3. Wildfly Exception Stack Trace of Issue: > {code} > 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > {code} > h3. SQL Server Profiler Stack Trace of Issue: > declare @p2 int > set @p2=-3 > declare @p3 nvarchar(max) > set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' > declare @p5 varbinary(max) > set @p5=NULL > exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output > select @p2, @p3, @p5 > h3. Possible Related Issues: > * https://issues.jboss.org/browse/JBTM-1433 > * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 6 16:23:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 6 May 2015 16:23:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2392) XA recovery exceptions In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2392. --------------------------------- Resolution: Duplicate Issue > XA recovery exceptions > ---------------------- > > Key: JBTM-2392 > URL: https://issues.jboss.org/browse/JBTM-2392 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Environment: wildfly-8.2.0.Final + Windows 7 + Microsoft SQL Server 2008 (SP2) + Microsoft JDBC 4.0 and 4.1 Drivers > Reporter: Mark S > Assignee: Tom Jenkinson > > h3. Wildfly Exception Stack Trace of Issue: > {code} > 12:12:42,427 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016008: Local XARecoveryModule.xaRecovery - caught exception: java.lang.NullPointerException > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:650) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > 12:12:42,431 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***" > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550) > at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:362) > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoverySecondPass(XARecoveryModule.java:740) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.bottomUpRecovery(XARecoveryModule.java:431) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkSecondPass(XARecoveryModule.java:212) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:789) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)] > {code} > h3. SQL Server Profiler Stack Trace of Issue: > declare @p2 int > set @p2=-3 > declare @p3 nvarchar(max) > set @p3=N'*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***' > declare @p5 varbinary(max) > set @p5=NULL > exec sp_execute 1, at p2 output, at p3 output,8388608, at p5 output > select @p2, @p3, @p5 > h3. Possible Related Issues: > * https://issues.jboss.org/browse/JBTM-1433 > * http://stackoverflow.com/questions/14476414/jboss-spamming-xa-recovery-warnings -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 7 04:18:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 7 May 2015 04:18:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2393: ----------------------------------- Summary: Add google analytics to the docs and narayana.io Key: JBTM-2393 URL: https://issues.jboss.org/browse/JBTM-2393 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Tom Jenkinson Assignee: Gytis Trikleris Fix For: 5.next For the docs, see an example here: https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 UA-XXXXXXX-X GTM-NJWS5L MyProject We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 05:31:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 05:31:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: Christian von Kutzleben created JBTM-2394: --------------------------------------------- Summary: Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption Key: JBTM-2394 URL: https://issues.jboss.org/browse/JBTM-2394 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Christian von Kutzleben Assignee: Tom Jenkinson The scenario is as follows: An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). The (lower-level) connection is --unsurprisingly-- a TCP/IP connection, and the RPC protocol --also unsurprisingly-- if of the form: "send data to server, then wait for server reply" At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) We could synchronized access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 05:37:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 05:37:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian von Kutzleben updated JBTM-2394: ------------------------------------------ Description: The scenario is as follows: An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). The application executes a query that takes longer than the configured timeout. The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). The (lower-level) connection is --unsurprisingly-- a TCP/IP connection, and the RPC protocol --also unsurprisingly-- if of the form: "send data to server, then wait for server reply" At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) We could synchronized access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. was: The scenario is as follows: An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). The (lower-level) connection is --unsurprisingly-- a TCP/IP connection, and the RPC protocol --also unsurprisingly-- if of the form: "send data to server, then wait for server reply" At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) We could synchronized access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is --unsurprisingly-- a TCP/IP connection, and > the RPC protocol --also unsurprisingly-- if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronized access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 05:39:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 05:39:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian von Kutzleben updated JBTM-2394: ------------------------------------------ Description: The scenario is as follows: An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). The application executes a query that takes longer than the configured timeout. The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). The (lower-level) connection is a TCP/IP connection, and the RPC protocol if of the form: "send data to server, then wait for server reply" At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. was: The scenario is as follows: An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). The application executes a query that takes longer than the configured timeout. The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). The (lower-level) connection is --unsurprisingly-- a TCP/IP connection, and the RPC protocol --also unsurprisingly-- if of the form: "send data to server, then wait for server reply" At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) We could synchronized access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 05:54:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 05:54:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2395: ----------------------------------- Summary: Correct Javadoc errors on JDK8 Key: JBTM-2395 URL: https://issues.jboss.org/browse/JBTM-2395 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 05:56:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 05:56:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066439#comment-13066439 ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-narayana/PROFILE=BLACKTIE,jdk=jdk8.latest,label=linux64el5/1062/console > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 06:02:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 06:02:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2396: ----------------------------------- Summary: Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time Key: JBTM-2396 URL: https://issues.jboss.org/browse/JBTM-2396 Project: JBoss Transaction Manager Issue Type: Task Components: STM Reporter: Tom Jenkinson Assignee: Mark Little While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. Consider the following test: {code} // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? Container theContainer1 = new Container(); Container theContainer2 = new Container(); // Setting up the two references to the STM object final Atomic obj1 = theContainer1.create(new ExampleSTM()); final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx AtomicAction a = new AtomicAction(); a.begin(); obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() // Setting up a second independent transaction and calling the @WriteLock method set() on it again AtomicAction.suspend(); AtomicAction b = new AtomicAction(); b.begin(); // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now obj2.set(12345); // This throws an exception even for @Optimisitic // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed {code} Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. >From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 06:04:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 06:04:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2396: -------------------------------- Attachment: OptimisticLockUnitTest.java I have attached a test that should show the error. > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 07:18:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 07:18:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2395: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/842 > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 07:19:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 07:19:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066462#comment-13066462 ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- The PR does disable the assembly of the javadocs into the distribution. Not sure if we want to keep that as we don't package the rest of the docs... > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 07:56:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 07:56:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066475#comment-13066475 ] Tom Jenkinson commented on JBTM-2394: ------------------------------------- I think you should open a discussion about this because the JTA spec allows for the behavior you are observing (3.4.3) so We can probably assist you better as a discussion. For example, @mmusgrov recently put together something to help JPA who did not want their synchronization called from a concurrent thread which might help you: JBTM-2342 and JBTM-2343 That being said, it is generally desirable that XAResources are rolled back immediately to avoid holding locks longer than necessary. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 07:56:46 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 07:56:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2394. --------------------------------- Resolution: Rejected > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:03:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 09:03:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2397) Update jboss-parent to allow building with required JDK8 updates such as findbugs In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2397: ----------------------------------- Summary: Update jboss-parent to allow building with required JDK8 updates such as findbugs Key: JBTM-2397 URL: https://issues.jboss.org/browse/JBTM-2397 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next Current version of parent is 17 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:04:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 09:04:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2397) Update jboss-parent to allow building with required JDK8 updates such as findbugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2397: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/842 > Update jboss-parent to allow building with required JDK8 updates such as findbugs > --------------------------------------------------------------------------------- > > Key: JBTM-2397 > URL: https://issues.jboss.org/browse/JBTM-2397 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Current version of parent is 17 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:23:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 09:23:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066498#comment-13066498 ] Christian von Kutzleben commented on JBTM-2394: ----------------------------------------------- Hi Tom, My interpretation of JTA 1.0.1, section 3.4.3 is a bit different from yours: IMO it focuses on "Different Java threads may be using the same connection resource to access the resource manager if the connection spans multiple method invocation." and not on "threads, XAResources, anything goes!" It does not specifically advocate that the current transaction reaper implementation is a viable approach. We can synchronize access to the connection currently associated with this XAResource, however then the transaction reaper thread can't do it's job. This change would be spec-compliant, the RPC protocol would not get corrupted, still, the reaper would not work. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:30:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 8 May 2015 09:30:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066501#comment-13066501 ] Michael Musgrove commented on JBTM-2390: ---------------------------------------- The port is giving me unusual results which I am investigating (I'll update the JIRA with the outcome). I am finding that a transaction with two participants is running 15 times more slowly than one with no participants. The number of requests in the two scenarios differ in the ratio 10:4 and one of them is doing disk writes but I would not expect that to account for a 15 fold difference. The two test scenarios are as follows: # client starts a (RTS) transaction and sends requests to two non transactional services. # client starts a (RTS) transaction and sends requests to two transactional services. The first scenario requires 4 http requests: * 1 request to the coordinator to begin a transaction * 2 non transactional service requests * 1 request to the coordinator to end the transaction The second scenario requires 10 http requests: * 1 request to the coordinator to begin a transaction * 2 transactional service requests ** 2 participant enlist requests to the coordinator * 1 request to the coordinator to end the transaction ** 2 prepare requests (one for each enlisted participant) ** 2 commit requests The benchmark output (on my laptop) for these two scenarios (I include the case of no transaction for completeness) is: {code} java -jar ArjunaJTA/jta/target/benchmarks.jar "org.jboss.narayana.rts.*TxnTest.*" -i 1 -wi 0 -f 1 -t 1 -r 100 Benchmark Mode Samples Score Score error Units o.j.n.r.EmptyTxnTest.testEmptyTxn thrpt 1 1447.812 NaN ops/s o.j.n.r.NoTxnTest.testNoTxn thrpt 1 4720.317 NaN ops/s o.j.n.r.TxnTest.testTxn thrpt 1 90.956 NaN ops/s {code} The benchmark with no transaction (two service requests) versus a transaction with no participants is slightly puzzling too since neither involves disk writing, uses half as many http requests and yet is 3 times faster (should have been twice as fast). I am running the coordinator and services on Undertow. I did try configs where the services were collocated with the coordinator and then when they were on different Undertow servers with no significant change in behaviour. > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:41:45 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 8 May 2015 09:41:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2340) Implement POC of MongoDB extension In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066503#comment-13066503 ] Gytis Trikleris commented on JBTM-2340: --------------------------------------- Code repository: https://github.com/Gytis/mongo-compensations-patent-poc > Implement POC of MongoDB extension > ---------------------------------- > > Key: JBTM-2340 > URL: https://issues.jboss.org/browse/JBTM-2340 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:44:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 09:44:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066504#comment-13066504 ] Tom Jenkinson commented on JBTM-2394: ------------------------------------- In that scenario the reaper would attempt to rollback the XAR a number of times (detecting the wedged resource) and finally it would give up trying to call rollback on the XAR and just call setRollbackOnly on the TX. I can say that the transaction reaper has been working in this manner successfully with many resource managers over the years. The reason we added JBTM-2342 is to assist with JPA which specifically is not thread-safe and the app server integration is required to call EntityManager.close() during afterCompletion(). You mentioned that you cannot use reaper thread names - this is entirely true and was considered during discussions on our forum regarding JBTM-2342. It was determined that this would not work in all scenarios as it is possible that a timed out transaction in a remote parent coordinator _may_ fire before the reaper anyway and in that case the rollback would come via (for example) Jacorb RequestProcessors and would be undetectable as a concurrent call. Hence JBTM-2342 provides an SPI to assist further. Alternatively, it would be possible for an XAResource implementation to detect concurrent access and use multiple (internal) connections to the database if that is a requirement of the implementation. I honestly feel that you will get better advice by discussing this on the forum. The transaction manager component (so Narayana) is not intended to be aware of connections. A caller invokes TX::enlist(XAResource). Callers do not provide us with "connections" or factories (I quote the word to signify it draw out how these can be JDBC/JMS/etc) to attempt to obtain an XAR from. Finally, as you point out the recovery manager is able to obtain XAR from helpers but the recovery manager has a very specific purpose and is not intended for this use case. Not that I would advocate a change in this area but if you were considering such a thing, determining which of the XAR registered with the recovery manager should be used to issue the rollback would be impossible as it stands. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:45:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 09:45:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066498#comment-13066498 ] Christian von Kutzleben edited comment on JBTM-2394 at 5/8/15 9:45 AM: ----------------------------------------------------------------------- Hi Tom, My interpretation of JTA 1.0.1, section 3.4.3 is a bit different from yours: IMO it focuses on "Different Java threads may be using the same connection resource to access the resource manager if the connection spans multiple method invocation." and not on "threads, XAResources, anything goes!" It does not specifically advocate that the current transaction reaper implementation is a viable approach. We can synchronize access to the connection currently associated with this XAResource, however then the transaction reaper thread can't do it's job. This change would be spec-compliant, the RPC protocol would not get corrupted, still, the reaper would not work. Edit: please also see the javadoc for XAConnection: "An XAConnection object may be enlisted in a distributed transaction by means of an XAResource object. A transaction manager, usually part of a middle tier server, manages an XAConnection object through the XAResource object." and the javadoc for PooledConnection's (base of XAConnection) getConnection() method. With this and a strict interpretation of JTA 3.4.3 one could imply, that access to the result of getConnection() (or it's underlying physical channel) should be synchronized; and if it is implemented that way, the reaper would be blocked forever. was (Author: cvk): Hi Tom, My interpretation of JTA 1.0.1, section 3.4.3 is a bit different from yours: IMO it focuses on "Different Java threads may be using the same connection resource to access the resource manager if the connection spans multiple method invocation." and not on "threads, XAResources, anything goes!" It does not specifically advocate that the current transaction reaper implementation is a viable approach. We can synchronize access to the connection currently associated with this XAResource, however then the transaction reaper thread can't do it's job. This change would be spec-compliant, the RPC protocol would not get corrupted, still, the reaper would not work. > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:54:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 09:54:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066511#comment-13066511 ] Tom Jenkinson commented on JBTM-2390: ------------------------------------- I am surprised you think its an anomaly. As an example, when you turn volatile store on our performance is something much more than a 15 fold improvement iirc? Some suggestions: 1. Are you using HQ store (can you use it in this config)? 2. Have you tried enabling the volatile store? In terms of notx vs emptytx I expect that is all down to the creation of the TX endpoints. You could profile the server to get more details there. I imagine your participants are no-ops so in the no tx case you have 2 no-op calls vs the empty tx case where you have 3 no-ops (I will class commit() here as a no-op as I assume it really is very little) and 1 op (the creation of the tx endpoints). Seems reasonable to me. In the emptytx case, can you drop the commit calls (without it falling over) to see the cost of the commit vs the create? > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 09:58:45 2015 From: issues at jboss.org (Christian von Kutzleben (JIRA)) Date: Fri, 8 May 2015 09:58:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066518#comment-13066518 ] Christian von Kutzleben commented on JBTM-2394: ----------------------------------------------- "Alternatively, it would be possible for an XAResource implementation to detect concurrent access and use multiple (internal) connections to the database if that is a requirement of the implementation. " I'm afraid, that a separate thread to connection mapping would make our XAResource implementation pretty unmaintainable. Two threads attached to the same Xid is a very special corner case (btw. the reaper does detect and report this in the log), it would be easy for us to implement a separate physical connection, if the reaper could identify itself as a "special" thread. "A caller invokes TX::enlist(XAResource). Callers do not provide us with "connections" or factories (I quote the word to signify it draw out how these can be JDBC/JMS/etc) to attempt to obtain an XAR from." Yes, that is indeed a problem of the JTA. I totally agree with you, that it is a technical problem to acquire an XAResource for such purposes, IMO JTA should be updated to provide such functionality, maybe a simple clone() specification for XAResource would be sufficient. (Btw. I updated my previous comment to include XAConnection references, while you were writing your reply) > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 10:09:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 10:09:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2394) Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066524#comment-13066524 ] Tom Jenkinson commented on JBTM-2394: ------------------------------------- I think we should move the discussion to the forum, you may find this class useful to consider: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/coordinator/CheckedAction.java It will alert you if a transaction is being completed while multiple threads are active in it. You can match uids with https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com/arjuna/ats/jta/transaction/Transaction.java#L67 If you do want to discuss it further I would definitely appreciate if you can move it to the forum so that it may act as a reference if other people in the future have similar requirements. Thanks, Tom > Transaction Reaper "abuses" in-use connection, leading to RPC protocol corruption > --------------------------------------------------------------------------------- > > Key: JBTM-2394 > URL: https://issues.jboss.org/browse/JBTM-2394 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Christian von Kutzleben > Assignee: Tom Jenkinson > > The scenario is as follows: > An regular JBoss application thread uses the connection associated with an XAResource for it's work with the database backend. Start(xid) had been invoked, which means, the associated connection is "switched" to that xid. After finishing work, the regular JBoss application thread would eventually call end(xid, TMSUCCESS). > The application executes a query that takes longer than the configured timeout. > The work with the database is done via database specific RPC invocations, caused by a enterprise bean (which uses the JPA API and the JPA implementation eventually talks to the database via the database protocol). > The (lower-level) connection is a TCP/IP connection, and > the RPC protocol if of the form: "send data to server, then wait for server reply" > At this point it should be clear, that the TCP/IP connection should not be shared by another thread whilst in the middle of an RPC invocation, because neither does the database server expect any data at this moment on this particular TCP/IP connection nor does it work, that then 2 threads wait on the same socket to receive a reply. (E.g. a ClosedByInterruptException is likely, there might be other error though, depending how wrong data is interpreted, e.g. BufferUnderflowException). > Unfortunately, this is exactly the behavior of the JBoss "Transaction Reaper" thread, that uses the very same XAResource, that had been used by the regular JBoss application thread and is currently associated to a connection, "switched" to the current xid. > By definition of the XA specification, any other XAResource could be used to terminate that transaction branch, and it would be fine, if the transaction reaper thread would use any XAResource (regular one, or one from our recovery module) to do that. > This is a conceptual flaw of the transaction reaper implementation, and we can't implement a workaround (except extremely silly things like reaper thread recognition by comparing thread names ...) > We could synchronize access to the TCP/IP connection, to not allow another thread communication, while another thread is active doing so, however, that kind of defeats the purpose of the reaper thread, as it would be blocked indefinitely. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 11:23:46 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 8 May 2015 11:23:46 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066555#comment-13066555 ] Michael Musgrove commented on JBTM-2390: ---------------------------------------- OK using horneq with (linux) asynchronous IO enabled and some other tweaks brings it to something more comparable (6 fold difference which when we factor in the extra http requests means a difference of 2-3 times), thanks: {code} Benchmark Mode Samples Score Score error Units o.j.n.r.EmptyTxnTest.testEmptyTxn thrpt 1 1494.553 NaN ops/s o.j.n.r.NoTxnTest.testNoTxn thrpt 1 5041.441 NaN ops/s o.j.n.r.TxnTest.testTxn thrpt 1 215.502 NaN ops/s {code} Note, I cannot try it out with the volatile store since RTS needs to list all uids for recovery purposes (and the volatile store doesn't support this op). > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 11:56:45 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 8 May 2015 11:56:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066578#comment-13066578 ] Tom Jenkinson commented on JBTM-2390: ------------------------------------- Maybe we should Jira to add that, it would just be a hashmap or something so shouldn't add much and might be more useful then. Just an idea. > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 12:06:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 8 May 2015 12:06:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2390: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/performance/pull/14 > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 12:14:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 8 May 2015 12:14:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2398: -------------------------------------- Summary: Support VolatileStore.allObjUids Key: JBTM-2398 URL: https://issues.jboss.org/browse/JBTM-2398 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Performance Testing Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.later This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 8 12:15:48 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 8 May 2015 12:15:48 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066586#comment-13066586 ] Michael Musgrove commented on JBTM-2390: ---------------------------------------- I agree since the volatile store is handy for providing a baseline > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat May 9 04:43:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 9 May 2015 04:43:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2390: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Changes pushed to the performance repo > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat May 9 04:44:45 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 9 May 2015 04:44:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2390) port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2390: ----------------------------------- Comment: was deleted (was: Changes pushed to the performance repo) > port the RTS test org.jboss.jbossts.star.test.PerformanceTest to a benchmark > ---------------------------------------------------------------------------- > > Key: JBTM-2390 > URL: https://issues.jboss.org/browse/JBTM-2390 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > Currently this test is run on an ad hoc basis on the NCL cluster. I would like it moved into the benchmark suite for more regular testing. > I have started work on this task but am finding threads deadlocking which has delayed the port. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat May 9 08:37:45 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sat, 9 May 2015 08:37:45 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2398) Support VolatileStore.allObjUids In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066668#comment-13066668 ] Mark Little commented on JBTM-2398: ----------------------------------- If you add it to VolatileStore then may as well also add it to TwoPhaseVolatileStore. > Support VolatileStore.allObjUids > --------------------------------- > > Key: JBTM-2398 > URL: https://issues.jboss.org/browse/JBTM-2398 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Performance Testing > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.later > > > This method is used by REST-AT and would be a useful addition for baselining the performance of the coordinator for comparison with non transactional and empty transaction requests. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 08:43:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 08:43:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066710#comment-13066710 ] Mark Little commented on JBTM-2396: ----------------------------------- You're right - for some reason the only use of OptimisticLock is within the actual tests. I'll take a look at this further when I get a chance. Will add your test too. > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 09:21:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 09:21:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2399) Consider adding optimistic write/read to LockMode and removing OptimisticLock In-Reply-To: References: Message-ID: Mark Little created JBTM-2399: --------------------------------- Summary: Consider adding optimistic write/read to LockMode and removing OptimisticLock Key: JBTM-2399 URL: https://issues.jboss.org/browse/JBTM-2399 Project: JBoss Transaction Manager Issue Type: Task Components: STM Affects Versions: 5.1.1 Reporter: Mark Little Assignee: Mark Little Would help simplify some of the OptimisticLockManager code duplication. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 09:24:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 09:24:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2399) Consider adding optimistic write/read to LockMode and removing OptimisticLock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066711#comment-13066711 ] Mark Little commented on JBTM-2399: ----------------------------------- If this is done then revert change to loadState in LockManager. See comment in code. > Consider adding optimistic write/read to LockMode and removing OptimisticLock > ----------------------------------------------------------------------------- > > Key: JBTM-2399 > URL: https://issues.jboss.org/browse/JBTM-2399 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Affects Versions: 5.1.1 > Reporter: Mark Little > Assignee: Mark Little > > Would help simplify some of the OptimisticLockManager code duplication. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 09:40:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 09:40:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1732) Durable STM instances require explicit sync to save state In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066712#comment-13066712 ] Mark Little commented on JBTM-1732: ----------------------------------- Same issue for Optimistic too if you share across containers using clone method. > Durable STM instances require explicit sync to save state > --------------------------------------------------------- > > Key: JBTM-1732 > URL: https://issues.jboss.org/browse/JBTM-1732 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > As with TXOJ, a persistent STM object isn't written to disk until a write lock is acquired on it within the scope of a transaction. Consider automating this at creation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 10:03:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 10:03:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066714#comment-13066714 ] Mark Little commented on JBTM-2396: ----------------------------------- There were a few things at work here. (i) the test used a couple of containers and cloned the object. That's legal but it exposed a bug in the way in which locks were saved and restored. They were created (in the first container) as OptimisticLock but restored (in the second container) as Lock which caused conflicts. That's fixed now but I may revisit the fix. See https://issues.jboss.org/browse/JBTM-2399 for more details. (ii) the OptimisticLock wasn't created by InvocationHandler, as you mentioned. (iii) because the test uses two containers and object invocations happen before any initial state has been saved for the instance, the activate for the copy fails - there's no state to load. This is a known issue (https://issues.jboss.org/browse/JBTM-1732). I changed the test to work around it for now. > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 10:04:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 10:04:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2396. ----------------------------- Resolution: Done > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 10:06:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 10:06:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2399) Consider adding optimistic write/read to LockMode and removing OptimisticLock In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066715#comment-13066715 ] Mark Little commented on JBTM-2399: ----------------------------------- Alternatively, since users are allowed to provide their own lock classes, extend LockManager and friends to work better with non-Lock instances. > Consider adding optimistic write/read to LockMode and removing OptimisticLock > ----------------------------------------------------------------------------- > > Key: JBTM-2399 > URL: https://issues.jboss.org/browse/JBTM-2399 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Affects Versions: 5.1.1 > Reporter: Mark Little > Assignee: Mark Little > > Would help simplify some of the OptimisticLockManager code duplication. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 10:08:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Sun, 10 May 2015 10:08:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066716#comment-13066716 ] Mark Little commented on JBTM-2396: ----------------------------------- Forgot to mention that the test had a comment about how commit should throw a LockException. That's not right. We only force the transaction to rollback if a conflict is detected at commit time. Then the test state that was assumed (1234) was also wrong, since the first transaction to commit actually makes the state 12345. I changed the test for both of these. > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sun May 10 18:23:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Sun, 10 May 2015 18:23:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066722#comment-13066722 ] Tom Jenkinson commented on JBTM-2396: ------------------------------------- I see the test passing now - thanks for the quick update :) re the LockException misconception I had, I now understand why throwing an exception is wrong here, though I wonder if it is worth trace logging something to help clarify if a TX is rolling back due to OCC conflict? > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 03:01:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 11 May 2015 03:01:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2396) Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066740#comment-13066740 ] Mark Little commented on JBTM-2396: ----------------------------------- If you add a JIRA I'll take a look :) > Investigate whether OCC implementation is unexpectedly checking locks during @WriteLock methods rather than delaying to commit time > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2396 > URL: https://issues.jboss.org/browse/JBTM-2396 > Project: JBoss Transaction Manager > Issue Type: Task > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > Attachments: OptimisticLockUnitTest.java > > > While checking out the STM work I tried to observe the difference between the OCC and PCC variants of the framework. During my testing I was not able to distinguish a difference between the two implementations. > Consider the following test: > {code} > // gonna confess here, I am using two containers as I thought it might separate better but I don't actually think this is required to use the two containers to get the separation as the two transactions should I create should be doing that? > Container theContainer1 = new Container(); > Container theContainer2 = new Container(); > // Setting up the two references to the STM object > final Atomic obj1 = theContainer1.create(new ExampleSTM()); > final Atomic obj2 = theContainer2.clone(new ExampleSTM(), obj1); > // Creating a transaction and calling the @WriteLock method set() on it but don't commit the tx > AtomicAction a = new AtomicAction(); > a.begin(); > obj1.set(1234); // Don't commit this yet - I want to check that a conflicting set() doesn't get the lockexception until commit() > // Setting up a second independent transaction and calling the @WriteLock method set() on it again > AtomicAction.suspend(); > AtomicAction b = new AtomicAction(); > b.begin(); > // Now, in my understanding calling this method should only throw a LockException for pessimistic locking, but with the current implementation the Lock throws a conflict now > obj2.set(12345); // This throws an exception even for @Optimisitic > // the rest of the test commits the two txs, but IMO as I am using @Optimistic I should not have got the LockException on the second set() so the test failed > {code} > Whether the Atomic interface is annotated with either @Optimisitic (or ommitted/default @Pessimisitc) the second @WriteLock set(int) call results in a lockexception being thrown. This is contrary to my expectations for OCC where I would expect to observe the set() being allowed but validation to be performed during commit and the commit to fail. > From my reading of STM/src/main/java/org/jboss/stm/internal/reflect/InvocationHandler.java I can see that this class (nor any of the other main classes) uses the OptimisticLock (which appears to suppress lock conflicts). I can see it uses OptimisticLockRecord which may do the validation correctly but my test fails because the second set(int) is allowed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 03:03:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Mon, 11 May 2015 03:03:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1732) Durable STM instances require explicit sync to save state In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066741#comment-13066741 ] Mark Little commented on JBTM-1732: ----------------------------------- Adding for completeness: the workaround (as with TXOJ) is to force write the state prior to any other users (threads, cloned instances or processes) using the object. > Durable STM instances require explicit sync to save state > --------------------------------------------------------- > > Key: JBTM-1732 > URL: https://issues.jboss.org/browse/JBTM-1732 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Mark Little > Priority: Optional > > As with TXOJ, a persistent STM object isn't written to disk until a write lock is acquired on it within the scope of a transaction. Consider automating this at creation time. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 03:05:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 11 May 2015 03:05:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2400: ----------------------------------- Summary: Add logging to help clarify if a TX is rolling back due to OCC conflict Key: JBTM-2400 URL: https://issues.jboss.org/browse/JBTM-2400 Project: JBoss Transaction Manager Issue Type: Feature Request Components: STM Reporter: Tom Jenkinson Assignee: Mark Little Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 04:50:23 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 11 May 2015 04:50:23 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066767#comment-13066767 ] Gytis Trikleris commented on JBTM-1679: --------------------------------------- [~tomjenkinson], maybe this would be worth pushing to 5.next? > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 05:29:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 11 May 2015 05:29:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066785#comment-13066785 ] Tom Jenkinson commented on JBTM-1679: ------------------------------------- Sure, go for it. > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 6.later > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 05:30:22 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 11 May 2015 05:30:22 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1679) Make @CompensationScoped beans available during recovery In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1679: ---------------------------------- Fix Version/s: 5.next (was: 6.later) > Make @CompensationScoped beans available during recovery > -------------------------------------------------------- > > Key: JBTM-1679 > URL: https://issues.jboss.org/browse/JBTM-1679 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: TXFramework, XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 05:42:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 05:42:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Remove deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Fix Version/s: 5.next > Remove deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi > ------------------------------------------------------------------------------------------------------------------ > > Key: JBTM-2212 > URL: https://issues.jboss.org/browse/JBTM-2212 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.jbossts.star.util has been deprecated\|org.jboss.resteasy.client\|org.jboss.resteasy.spi has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java:[50,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[55,7] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[85,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[128,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[155,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[173,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[198,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[219,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[264,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[273,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[278,16] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[283,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[288,19] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[293,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[339,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[400,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[505,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[587,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[92,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[98,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[102,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[113,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[136,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[183,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[184,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[204,56] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[228,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[229,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[230,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[306,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[307,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[308,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[310,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[311,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[312,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[346,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[366,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[406,22] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[460,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[523,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[538,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[596,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[627,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[651,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[284,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[313,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[317,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[192,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[219,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[218,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[224,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[259,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[258,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[264,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[321,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[323,59] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[328,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[388,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[432,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[27,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[22,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[28,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[177,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[180,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[304,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[335,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[342,42] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[403,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[513,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[621,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[693,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[768,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[70,47] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[104,34] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[54,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[56,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[62,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[398,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[497,38] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[696,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[699,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[704,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[732,26] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[23,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[32,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[5,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[18,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[27,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[8,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[18,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[19,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[20,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[89,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[56,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[79,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[103,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[119,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[127,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[131,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[295,17] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[307,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[309,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[311,52] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[24,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,42] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,41] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,49] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[164,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[15,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[13,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[14,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[20,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[21,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[23,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[38,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[42,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[178,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[205,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[228,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[247,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[266,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[285,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[304,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[321,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[340,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,57] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[83,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[98,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[102,9] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[115,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[118,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[121,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[122,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[136,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[149,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[152,68] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[166,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[169,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[184,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[198,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[213,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[225,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[242,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[254,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[271,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[289,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[301,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[320,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[321,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[324,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[325,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[328,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[330,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[329,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[333,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[335,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[334,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[338,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[340,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[339,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[343,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[345,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[344,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[349,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[350,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[68,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[94,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[113,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[114,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[117,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[119,57] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[118,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[32,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[41,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[75,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[92,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[72,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[104,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[123,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[71,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[79,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[94,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[109,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[124,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[136,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[141,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 05:42:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 05:42:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Summary: Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi (was: Remove deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi) > Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi > -------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2212 > URL: https://issues.jboss.org/browse/JBTM-2212 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.jbossts.star.util has been deprecated\|org.jboss.resteasy.client\|org.jboss.resteasy.spi has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java:[50,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[55,7] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[85,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[128,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[155,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[173,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[198,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[219,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[264,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[273,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[278,16] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[283,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[288,19] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[293,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[339,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[400,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[505,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[587,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[92,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[98,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[102,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[113,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[136,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[183,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[184,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[204,56] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[228,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[229,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[230,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[306,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[307,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[308,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[310,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[311,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[312,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[346,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[366,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[406,22] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[460,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[523,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[538,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[596,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[627,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[651,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[284,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[313,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[317,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[192,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[219,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[218,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[224,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[259,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[258,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[264,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[321,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[323,59] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[328,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[388,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[432,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[27,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[22,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[28,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[177,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[180,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[304,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[335,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[342,42] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[403,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[513,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[621,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[693,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[768,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[70,47] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[104,34] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[54,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[56,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[62,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[398,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[497,38] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[696,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[699,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[704,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[732,26] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[23,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[32,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[5,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[18,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[27,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[8,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[18,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[19,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[20,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[89,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[56,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[79,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[103,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[119,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[127,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[131,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[295,17] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[307,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[309,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[311,52] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[24,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,42] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,41] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,49] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[164,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[15,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[13,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[14,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[20,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[21,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[23,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[38,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[42,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[178,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[205,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[228,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[247,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[266,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[285,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[304,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[321,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[340,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,57] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[83,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[98,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[102,9] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[115,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[118,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[121,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[122,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[136,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[149,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[152,68] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[166,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[169,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[184,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[198,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[213,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[225,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[242,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[254,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[271,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[289,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[301,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[320,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[321,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[324,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[325,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[328,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[330,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[329,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[333,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[335,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[334,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[338,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[340,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[339,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[343,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[345,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[344,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[349,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[350,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[68,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[94,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[113,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[114,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[117,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[119,57] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[118,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[32,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[41,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[75,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[92,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[72,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[104,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[123,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[71,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[79,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[94,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[109,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[124,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[136,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[141,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 05:44:21 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 05:44:21 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Summary: Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling (was: Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client and org.jboss.resteasy.spi) > Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2212 > URL: https://issues.jboss.org/browse/JBTM-2212 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.jbossts.star.util has been deprecated\|org.jboss.resteasy.client\|org.jboss.resteasy.spi has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java:[50,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[55,7] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[85,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[128,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[155,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[173,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[198,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[219,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[264,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[273,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[278,16] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[283,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[288,19] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[293,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[339,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[400,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[505,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[587,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[92,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[98,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[102,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[113,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[136,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[183,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[184,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[204,56] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[228,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[229,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[230,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[306,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[307,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[308,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[310,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[311,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[312,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[346,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[366,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[406,22] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[460,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[523,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[538,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[596,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[627,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[651,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[284,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[313,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[317,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[192,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[219,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[218,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[224,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[259,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[258,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[264,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[321,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[323,59] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[328,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[388,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[432,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[27,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[22,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[28,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[177,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[180,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[304,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[335,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[342,42] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[403,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[513,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[621,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[693,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[768,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[70,47] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[104,34] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[54,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[56,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[62,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[398,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[497,38] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[696,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[699,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[704,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[732,26] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[23,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[32,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[5,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[18,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[27,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[8,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[18,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[19,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[20,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[89,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[56,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[79,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[103,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[119,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[127,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[131,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[295,17] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[307,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[309,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[311,52] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[24,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,42] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,41] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,49] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[164,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[15,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[13,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[14,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[20,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[21,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[23,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[38,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[42,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[178,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[205,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[228,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[247,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[266,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[285,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[304,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[321,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[340,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,57] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[83,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[98,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[102,9] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[115,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[118,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[121,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[122,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[136,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[149,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[152,68] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[166,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[169,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[184,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[198,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[213,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[225,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[242,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[254,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[271,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[289,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[301,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[320,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[321,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[324,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[325,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[328,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[330,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[329,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[333,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[335,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[334,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[338,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[340,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[339,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[343,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[345,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[344,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[349,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[350,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[68,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[94,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[113,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[114,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[117,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[119,57] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[118,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[32,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[41,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[75,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[92,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[72,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[104,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[123,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[71,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[79,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[94,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[109,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[124,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[136,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[141,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 06:31:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 06:31:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2212) Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2212: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > Minimize deprecation warnings for org.jboss.jbossts.star.util, org.jboss.resteasy.client, org.jboss.resteasy.spi and tooling > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2212 > URL: https://issues.jboss.org/browse/JBTM-2212 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.later > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.jbossts.star.util has been deprecated\|org.jboss.resteasy.client\|org.jboss.resteasy.spi has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/util/src/main/java/org/jboss/jbossts/star/util/TxSupport.java:[50,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[55,7] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[85,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[128,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[155,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[173,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[198,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[219,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[264,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[273,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[278,16] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[283,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[288,19] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[293,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[339,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[400,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[505,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[587,11] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[92,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[98,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[102,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[113,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[136,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[183,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[184,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[204,56] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[228,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[229,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[230,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[306,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[307,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[308,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[310,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[311,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[312,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[346,23] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[366,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[406,22] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[460,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[523,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[538,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[596,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[627,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/service/Coordinator.java:[651,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[284,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[313,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/Transaction.java:[317,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[192,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[219,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[218,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[224,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[259,55] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[258,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[264,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[307,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[321,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[323,59] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[328,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[388,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[386,21] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/main/java/org/jboss/jbossts/star/resource/RESTRecord.java:[432,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[27,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[22,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[28,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[177,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[180,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[304,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[335,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[342,42] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[403,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[414,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[455,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[507,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[513,27] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[621,31] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[693,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/BaseTest.java:[768,20] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[45,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[72,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[112,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[141,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[142,30] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[199,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/OptionalSpecTest.java:[261,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[70,47] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[104,34] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,13] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/PerformanceTest.java:[125,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/TxSupportTest.java:[36,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[53,50] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[54,28] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[56,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[62,14] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[74,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[100,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[126,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[160,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[193,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[228,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/CoordinatorTest.java:[242,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[51,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[150,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[196,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[222,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[246,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[274,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[302,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[331,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[372,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[398,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[427,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[458,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[481,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[497,38] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[535,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[587,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[671,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[696,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[699,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[704,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[731,58] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/tx/src/test/java/org/jboss/jbossts/star/test/SpecTest.java:[732,26] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[23,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/webservice/src/test/java/org/jboss/jbossts/star/test/ClientIntegrationTest.java:[32,24] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[5,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[18,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[27,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[8,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[18,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[19,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[20,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/VolatileParticipantResource.java:[89,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[56,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[79,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[103,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[119,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[127,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[131,41] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[295,17] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[307,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[309,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantResource.java:[311,52] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/HeuristicMapper.java:[24,37] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[235,42] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,15] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[237,41] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/RecoveryManager.java:[241,49] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,9] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[143,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/main/java/org/jboss/narayana/rest/integration/ParticipantsManagerImpl.java:[164,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[15,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[13,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[14,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[11,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[20,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[21,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[23,30] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[6,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[38,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/AbstractIntegrationTestCase.java:[42,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[178,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[205,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[228,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[247,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[266,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[285,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[304,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[321,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/BasicIntegrationTestCase.java:[340,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[130,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[138,53] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,19] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/integration/RecoveryIntegrationTestCase.java:[146,57] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[83,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[98,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[102,9] org.jboss.resteasy.spi.Link in org.jboss.resteasy.spi has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[115,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[118,46] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[121,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[122,45] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[130,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[136,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[149,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[152,68] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[166,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[169,66] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[184,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[198,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[213,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[225,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[242,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[254,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[271,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[289,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[301,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[320,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[321,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[324,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[325,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[328,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[330,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[329,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[333,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[335,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[334,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[338,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[340,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[339,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[343,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[345,17] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[344,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[349,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/ParticipantResourceTestCase.java:[350,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[68,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[80,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[94,9] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[113,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[114,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[117,13] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[119,57] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/integration/src/test/java/org/jboss/narayana/rest/integration/test/functional/VolatileParticipantResourceTestCase.java:[118,20] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[32,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[41,35] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[11,33] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[12,33] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[75,15] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AbstractTestCase.java:[92,25] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[72,33] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[104,29] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/common/LoggingRestATResource.java:[123,32] org.jboss.jbossts.star.util.TxSupport in org.jboss.jbossts.star.util has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[71,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[79,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[86,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[94,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[102,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[109,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[116,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[124,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[132,45] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[136,15] org.jboss.resteasy.client.ClientResponse in org.jboss.resteasy.client has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/rts/at/bridge/src/test/java/org/jboss/narayana/rest/bridge/inbound/test/integration/AnnotationsTestCase.java:[141,24] org.jboss.resteasy.client.ClientRequest in org.jboss.resteasy.client has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 06:45:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 06:45:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2401) Benchmark hang running product comparison tests In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2401: -------------------------------------- Summary: Benchmark hang running product comparison tests Key: JBTM-2401 URL: https://issues.jboss.org/browse/JBTM-2401 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove Assignee: Michael Musgrove The JMH benchmarking framework hung running io.narayana.perf.product.ProductComparison.testJotm during the following CI job: http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/12 Please refer to the attached file for the jstack dump -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 06:46:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 06:46:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2401) Benchmark hang running product comparison tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2401: ----------------------------------- Priority: Minor (was: Major) > Benchmark hang running product comparison tests > ----------------------------------------------- > > Key: JBTM-2401 > URL: https://issues.jboss.org/browse/JBTM-2401 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > > The JMH benchmarking framework hung running io.narayana.perf.product.ProductComparison.testJotm during the following CI job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/12 > Please refer to the attached file for the jstack dump -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 06:50:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 06:50:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2401) Benchmark hang running product comparison tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2401: ----------------------------------- Attachment: 8857.jstack The jstack output does not show anything obvious: it shows the JMH benchmark runner waiting for termination the benchmark. > Benchmark hang running product comparison tests > ----------------------------------------------- > > Key: JBTM-2401 > URL: https://issues.jboss.org/browse/JBTM-2401 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 8857.jstack > > > The JMH benchmarking framework hung running io.narayana.perf.product.ProductComparison.testJotm during the following CI job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/12 > Please refer to the attached file for the jstack dump -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 06:52:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 11 May 2015 06:52:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2401) Benchmark hang running product comparison tests In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066822#comment-13066822 ] Michael Musgrove edited comment on JBTM-2401 at 5/11/15 6:51 AM: ----------------------------------------------------------------- The jstack output does not show anything obvious: it shows the JMH benchmark runner waiting for termination the benchmark. The same job ran successfully on the NCL cluster around on the same software was (Author: mmusgrov): The jstack output does not show anything obvious: it shows the JMH benchmark runner waiting for termination the benchmark. > Benchmark hang running product comparison tests > ----------------------------------------------- > > Key: JBTM-2401 > URL: https://issues.jboss.org/browse/JBTM-2401 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Attachments: 8857.jstack > > > The JMH benchmarking framework hung running io.narayana.perf.product.ProductComparison.testJotm during the following CI job: > http://albany.eng.hst.ams2.redhat.com/job/narayana-benchmarks/12 > Please refer to the attached file for the jstack dump -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 11 08:52:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 11 May 2015 08:52:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2402) Create a quickstart and some docs that show how to use our OSGi bundle In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2402: ----------------------------------- Summary: Create a quickstart and some docs that show how to use our OSGi bundle Key: JBTM-2402 URL: https://issues.jboss.org/browse/JBTM-2402 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Application Server Integration, Demonstrator, Documentation Reporter: Tom Jenkinson Assignee: Amos Feng We should create a quickstart to demonstrate how to install and use our bundle. It should also be described in our project (community) manual. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 12 06:09:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 12 May 2015 06:09:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2403) Add a quickstart for Undertow + REST-AT + JAX-RS In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2403: -------------------------------------- Summary: Add a quickstart for Undertow + REST-AT + JAX-RS Key: JBTM-2403 URL: https://issues.jboss.org/browse/JBTM-2403 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.next Undertow + REST-AT + JAX-RS is a good simple showcase of our projects. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 12 07:54:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 12 May 2015 07:54:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2403) Add a quickstart for Undertow + REST-AT + JAX-RS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2403: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/137 > Add a quickstart for Undertow + REST-AT + JAX-RS > ------------------------------------------------ > > Key: JBTM-2403 > URL: https://issues.jboss.org/browse/JBTM-2403 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Undertow + REST-AT + JAX-RS is a good simple showcase of our projects. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 12 12:45:27 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 12 May 2015 12:45:27 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2369: ----------------------------------- Fix Version/s: 5.next (was: 5.later) > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 12 12:46:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 12 May 2015 12:46:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2369. ------------------------------------ Resolution: Done I have added a (bash) script for collecting the info (narayana/scripts/hudson/hw.sh) and updated the pull job config (job/btny-pulls-narayana) on the NCL cluster > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 05:03:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 05:03:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067380#comment-13067380 ] Michael Musgrove edited comment on JBTM-2369 at 5/13/15 5:02 AM: ----------------------------------------------------------------- I have added a (bash) script for collecting the info (narayana/scripts/hudson/hw.sh) and updated the pull job config (job/btny-pulls-narayana) on the NCL cluster. I can see a minor issue here though since the hw info output is presented as a CI build artefact was (Author: mmusgrov): I have added a (bash) script for collecting the info (narayana/scripts/hudson/hw.sh) and updated the pull job config (job/btny-pulls-narayana) on the NCL cluster > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 05:03:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 05:03:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-2369: ------------------------------------ Reopening in order to add the missing PR link > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 05:04:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 05:04:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2369: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/844 > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 05:50:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 13 May 2015 05:50:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2213) Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2213: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove deprecation warnings for org.jboss.narayana.txframework.api.annotation.lifecycle.ba > ------------------------------------------------------------------------------------------ > > Key: JBTM-2213 > URL: https://issues.jboss.org/browse/JBTM-2213 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "org.jboss.narayana.txframework.api.annotation.lifecycle.ba" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipant.java:[45,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[31,66] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[112,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[154,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[115,10] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[162,6] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[57,146] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[115,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/coordinatorCompletion/BACoordinatorCompletionService.java:[158,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[62,27] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[65,130] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[118,32] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/functional/ws/ba/participantCompletion/BAParticipantCompletionService.java:[166,18] org.jboss.narayana.txframework.api.annotation.lifecycle.ba.Unknown in org.jboss.narayana.txframework.api.annotation.lifecycle.ba has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 05:50:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 13 May 2015 05:50:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2214) Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2214: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove deprecation warnings for com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2214 > URL: https://issues.jboss.org/browse/JBTM-2214 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 5.0.2 > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > If you run: > ./build.sh clean install -DskipTests | grep "com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated" > You will see: > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithParticipantCompletionStub.java:[173,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/SubordinateCoordinatorCompletionParticipantStub.java:[260,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/WS-T/dev/src/com/arjuna/wst11/stub/BusinessAgreementWithCoordinatorCompletionStub.java:[207,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[64,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[59,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestNoExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[62,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestFaultedExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[60,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/FailureBusinessParticipant.java:[106,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wstx/tests/common/DemoBusinessParticipant.java:[100,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestSystemExceptionBusinessAgreementWithParticipantCompletionParticipant.java:[63,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/unit/src/test/java/com/arjuna/wst/tests/common/TestWrongStateExceptionBusinessAgreementWithCoordinatorCompletionParticipant.java:[67,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/WSTX11-interop/src/main/java/com/jboss/transaction/txinterop/webservices/bainterop/participant/ParticipantCompletionParticipantAdapter.java:[56,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/XTS/localjunit/xtstest/src/org/jboss/jbossts/xts/servicetests/service/participant/ParticipantCompletionTestParticipant.java:[99,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/ParticipantImpl.java:[144,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/main/java/org/jboss/narayana/compensations/impl/remote/RemoteParticipant.java:[81,17] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBACoordinatorCompletionParticipantTest.java:[113,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated > [WARNING] /home/tom/projects/jbosstm/narayana/txframework/src/test/java/org/jboss/narayana/txframework/impl/handlers/wsba/WSBAParticipantCompletionParticipantTest.java:[116,21] unknown() in com.arjuna.wst.BusinessAgreementWithParticipantCompletionParticipant has been deprecated -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 06:35:21 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 13 May 2015 06:35:21 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067600#comment-13067600 ] Gytis Trikleris commented on JBTM-2393: --------------------------------------- [~tomjenkinson], do we have analytics id etc.? > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 06:57:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 06:57:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2404: -------------------------------------- Summary: narayana-codeCoverage CI job is not producing any output Key: JBTM-2404 URL: https://issues.jboss.org/browse/JBTM-2404 Project: JBoss Transaction Manager Issue Type: Bug Components: Configuration Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 08:55:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 08:55:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2369: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 09:39:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 09:39:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067700#comment-13067700 ] Michael Musgrove commented on JBTM-2404: ---------------------------------------- The failure is because we only run PROFILE=MAIN on the code coverage job. So I can fix it by any combination of the following: 1. skip the run the QA jacoco report (ie remove the line ant -f run-tests.xml jacoco-report from the job config) 2. conditionally run the QA jacoco report task based on the presence of QA execution data 3. update the CI job to run a profile that includes QA testing My plan is to fix it using option 3 > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 10:26:20 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 10:26:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2404: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/845 > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 11:38:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 13 May 2015 11:38:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067774#comment-13067774 ] Tom Jenkinson commented on JBTM-2404: ------------------------------------- Yeah, sorry it was my mistake I have been trying to remove the app server tests from being ran (so the job can stay on JDK7) but when I tried to put RTS_AS_TESTS=0 those tests are still ran. I managed to disable the OSGi tests but can't get the RTS ones suppressed :( Thanks for looking into it mike. > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 13 14:08:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 13 May 2015 14:08:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067812#comment-13067812 ] Michael Musgrove commented on JBTM-2395: ---------------------------------------- There are more javadoc errors - I am working my through them (http://albany.eng.hst.ams2.redhat.com/job/btny-pulls-quickstart/92/console) > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 03:09:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 14 May 2015 03:09:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067904#comment-13067904 ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- The strange thing is I think I fixed those. This one (the first one) in particular was fixed: [ERROR] Exit code: 1 - /home/hudson/workspace/btny-pulls-quickstart/narayana/ArjunaCore/arjuna/classes/com/arjuna/ats/arjuna/tools/stats/TxPerfGraph.java:716: error: package org.jfree.beans does not exist > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 03:10:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 14 May 2015 03:10:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067907#comment-13067907 ] Tom Jenkinson commented on JBTM-2395: ------------------------------------- It was fixed by this bit: https://github.com/jbosstm/narayana/blob/143e65b55de87d9ac18f7e2e1f0be2fbe49bd3e5/ArjunaCore/arjunacore/pom.xml#L161 I think what could be going on is the -Pcommunity profile isn't being set in that build? > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 05:12:21 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 05:12:21 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite test failure: CrashRecovery05_1 Test04 In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2405: ------------------------------------- Summary: QA suite test failure: CrashRecovery05_1 Test04 Key: JBTM-2405 URL: https://issues.jboss.org/browse/JBTM-2405 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 05:22:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 05:22:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BAParticipantCompletionTest test failed because of the race condition In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2406: ------------------------------------- Summary: BAParticipantCompletionTest test failed because of the race condition Key: JBTM-2406 URL: https://issues.jboss.org/browse/JBTM-2406 Project: JBoss Transaction Manager Issue Type: Bug Components: TXFramework Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.later http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ {code} ------------------------------------------------------------------------------- Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest ------------------------------------------------------------------------------- Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 09:21:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 09:21:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2407) Remove CDIExtensionProcessor in the XTS subsytem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris moved WFLY-4629 to JBTM-2407: --------------------------------------------- Project: JBoss Transaction Manager (was: WildFly) Key: JBTM-2407 (was: WFLY-4629) Component/s: XTS (was: XTS) Fix Version/s: 5.next (was: 10.0.0.Alpha1) > Remove CDIExtensionProcessor in the XTS subsytem > ------------------------------------------------ > > Key: JBTM-2407 > URL: https://issues.jboss.org/browse/JBTM-2407 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem. > There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 09:57:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 09:57:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2408) Remove CDI extension descriptors from compensations quickstarts In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2408: ------------------------------------- Summary: Remove CDI extension descriptors from compensations quickstarts Key: JBTM-2408 URL: https://issues.jboss.org/browse/JBTM-2408 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator, TXFramework Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Minor Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 10:02:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 10:02:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2407) Remove CDIExtensionProcessor in the XTS subsytem In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2407: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/847, https://github.com/jbosstm/jboss-as/pull/41 > Remove CDIExtensionProcessor in the XTS subsytem > ------------------------------------------------ > > Key: JBTM-2407 > URL: https://issues.jboss.org/browse/JBTM-2407 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > WFLY-1370 removes the need for the CDIExtensionProcessor in the XTS subsytem. > There is currently a hack in CDIExtensionProcessor in 5_BRANCH. This MUST be removed if WFLY-1370 is not merged in time for release. Hence I have marked this as critical. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 11:19:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 11:19:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1967) org.jboss.jbossts.xts.bytemanSupport.BMScript fails to submit/remove rules on remote container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris resolved JBTM-1967. ----------------------------------- Fix Version/s: (was: 6.later) Resolution: Out of Date Issues must have beet fixed somewhere upstream. Does not fail any more. > org.jboss.jbossts.xts.bytemanSupport.BMScript fails to submit/remove rules on remote container > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1967 > URL: https://issues.jboss.org/browse/JBTM-1967 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > TXFramework tests fail to add and remove byteman script to/from remote server. > Here is the output after executing the following line: > {code}mvn clean test -Dtest=CompensatableTest#testDefaultNoExistingTX -Parq-remote{code} > {code} > Running org.jboss.narayana.compensations.functional.compensatable.CompensatableTest > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.167 sec <<< FAILURE! > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.166 sec <<< ERROR! > java.lang.RuntimeException: Failed to submit Byteman script > at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:24) > at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.submitBytemanScript(CompensatableTest.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:579) > at java.net.Socket.connect(Socket.java:528) > at java.net.Socket.(Socket.java:425) > at java.net.Socket.(Socket.java:208) > at org.jboss.byteman.agent.submit.Submit$Comm.(Submit.java:871) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777) > at org.jboss.byteman.agent.submit.Submit.addScripts(Submit.java:595) > at org.jboss.byteman.agent.submit.Submit.addRulesFromResources(Submit.java:568) > at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:22) > ... 54 more > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.167 sec <<< ERROR! > java.lang.RuntimeException: Failed to remove Byteman script > at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:34) > at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.removeBytemanScript(CompensatableTest.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:579) > at java.net.Socket.connect(Socket.java:528) > at java.net.Socket.(Socket.java:425) > at java.net.Socket.(Socket.java:208) > at org.jboss.byteman.agent.submit.Submit$Comm.(Submit.java:871) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:688) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromResources(Submit.java:661) > at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:32) > ... 54 more > Results : > Tests in error: > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to submit Byteman script > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to remove Byteman script > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 11:19:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 11:19:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1967) org.jboss.jbossts.xts.bytemanSupport.BMScript fails to submit/remove rules on remote container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris closed JBTM-1967. --------------------------------- > org.jboss.jbossts.xts.bytemanSupport.BMScript fails to submit/remove rules on remote container > ---------------------------------------------------------------------------------------------- > > Key: JBTM-1967 > URL: https://issues.jboss.org/browse/JBTM-1967 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > > TXFramework tests fail to add and remove byteman script to/from remote server. > Here is the output after executing the following line: > {code}mvn clean test -Dtest=CompensatableTest#testDefaultNoExistingTX -Parq-remote{code} > {code} > Running org.jboss.narayana.compensations.functional.compensatable.CompensatableTest > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 6.167 sec <<< FAILURE! > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.166 sec <<< ERROR! > java.lang.RuntimeException: Failed to submit Byteman script > at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:24) > at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.submitBytemanScript(CompensatableTest.java:86) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.beforeClass(EventTestRunnerAdaptor.java:80) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:182) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:579) > at java.net.Socket.connect(Socket.java:528) > at java.net.Socket.(Socket.java:425) > at java.net.Socket.(Socket.java:208) > at org.jboss.byteman.agent.submit.Submit$Comm.(Submit.java:871) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777) > at org.jboss.byteman.agent.submit.Submit.addScripts(Submit.java:595) > at org.jboss.byteman.agent.submit.Submit.addRulesFromResources(Submit.java:568) > at org.jboss.jbossts.xts.bytemanSupport.BMScript.submit(BMScript.java:22) > ... 54 more > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest Time elapsed: 6.167 sec <<< ERROR! > java.lang.RuntimeException: Failed to remove Byteman script > at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:34) > at org.jboss.narayana.compensations.functional.compensatable.CompensatableTest.removeBytemanScript(CompensatableTest.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:36) > at org.jboss.arquillian.junit.Arquillian$StatementLifecycleExecutor.invoke(Arquillian.java:351) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.execute(ClientBeforeAfterLifecycleEventExecuter.java:99) > at org.jboss.arquillian.container.test.impl.execution.ClientBeforeAfterLifecycleEventExecuter.on(ClientBeforeAfterLifecycleEventExecuter.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.afterClass(EventTestRunnerAdaptor.java:87) > at org.jboss.arquillian.junit.Arquillian$3$1.evaluate(Arquillian.java:204) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:300) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:242) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:137) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) > Caused by: java.net.ConnectException: Connection refused > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) > at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:579) > at java.net.Socket.connect(Socket.java:528) > at java.net.Socket.(Socket.java:425) > at java.net.Socket.(Socket.java:208) > at org.jboss.byteman.agent.submit.Submit$Comm.(Submit.java:871) > at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:777) > at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:688) > at org.jboss.byteman.agent.submit.Submit.deleteRulesFromResources(Submit.java:661) > at org.jboss.jbossts.xts.bytemanSupport.BMScript.remove(BMScript.java:32) > ... 54 more > Results : > Tests in error: > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to submit Byteman script > org.jboss.narayana.compensations.functional.compensatable.CompensatableTest: Failed to remove Byteman script > Tests run: 2, Failures: 0, Errors: 2, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 12:40:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 12:40:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2393: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana.io/pull/3 > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 12:53:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 14 May 2015 12:53:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2409: -------------------------------------- Summary: XARecoveryModuleHelpersUnitTest hang Key: JBTM-2409 URL: https://issues.jboss.org/browse/JBTM-2409 Project: JBoss Transaction Manager Issue Type: Bug Components: Recovery Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. The junit test thread: - starts 2 threads that will remove a recovery helper - triggers xaRecoveryModule.periodicWorkFirstPass() - triggers xaRecoveryModule.periodicWorkSecondPass() - joins with remover threads The jstack output shows: - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; - the junit test thread is waiting to join with these two threads; Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 12:54:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 14 May 2015 12:54:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2409) XARecoveryModuleHelpersUnitTest hang In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2409: ----------------------------------- Attachment: 32287.jstack > XARecoveryModuleHelpersUnitTest hang > ------------------------------------ > > Key: JBTM-2409 > URL: https://issues.jboss.org/browse/JBTM-2409 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: 32287.jstack > > > The test checks that recovery helpers can be removed at the correct stages during recovery scans. The CI job http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/196 shows the hang. > The junit test thread: > - starts 2 threads that will remove a recovery helper > - triggers xaRecoveryModule.periodicWorkFirstPass() > - triggers xaRecoveryModule.periodicWorkSecondPass() > - joins with remover threads > The jstack output shows: > - the two threads in the process of removing a recovery helper and are waiting for the first pass to finish; > - the junit test thread is waiting to join with these two threads; > Since both recovery passes must have completed it looks like the remover threads weren't notified when the first pass completed. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 14 13:25:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 14 May 2015 13:25:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068156#comment-13068156 ] Gytis Trikleris commented on JBTM-2393: --------------------------------------- [~tomjenkinson], where did you find that docs example? That pressgang thing seems like dying > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 08:40:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 15 May 2015 08:40:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068382#comment-13068382 ] Mark Little commented on JBTM-2400: ----------------------------------- A comment for completeness only: trace is enabled then the user will see something from BasicAction when End fails to commit the transaction. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 08:42:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 15 May 2015 08:42:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2410) Internationalize warning/info messages In-Reply-To: References: Message-ID: Mark Little created JBTM-2410: --------------------------------- Summary: Internationalize warning/info messages Key: JBTM-2410 URL: https://issues.jboss.org/browse/JBTM-2410 Project: JBoss Transaction Manager Issue Type: Task Components: STM Affects Versions: 5.1.1 Reporter: Mark Little Assignee: Mark Little Some of them aren't at the moment. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 09:09:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 15 May 2015 09:09:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2411: ----------------------------------- Summary: Investigate jgroups-raft and whether this can help with cloud object store Key: JBTM-2411 URL: https://issues.jboss.org/browse/JBTM-2411 Project: JBoss Transaction Manager Issue Type: Task Components: Recovery, Transaction Core Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.later http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 09:43:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Fri, 15 May 2015 09:43:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2393: ---------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana.io/pull/3, https://github.com/jbosstm/narayana/pull/848, https://github.com/jbosstm/documentation/pull/31 (was: https://github.com/jbosstm/narayana.io/pull/3) All pull requests are ready for review. For now I have added the same analytics id everywhere. If this will not work, we can improve it. > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 09:46:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 15 May 2015 09:46:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068411#comment-13068411 ] Mark Little commented on JBTM-2400: ----------------------------------- I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 09:46:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 15 May 2015 09:46:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068411#comment-13068411 ] Mark Little edited comment on JBTM-2400 at 5/15/15 9:45 AM: ------------------------------------------------------------ I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info/trace. was (Author: marklittle): I added a warning message to the lock record if it forces a rollback due to state change. I'm still not sure if this may output too many warnings, especially as the number of conflicts occur (amount of contention increases with threads etc.) So we may want to revisit this eventually and turn it into an info. > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 09:46:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 15 May 2015 09:46:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2400) Add logging to help clarify if a TX is rolling back due to OCC conflict In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Little closed JBTM-2400. ----------------------------- Resolution: Done > Add logging to help clarify if a TX is rolling back due to OCC conflict > ----------------------------------------------------------------------- > > Key: JBTM-2400 > URL: https://issues.jboss.org/browse/JBTM-2400 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Currently if a transaction including an STM object aborts due to an OCC violation then nothing is logged to assist a user with understanding the reason for the rollback. > I am wondering whether this should be a TRACE or even WARN to match what would happen with other (say XA) resource managers. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 11:20:19 2015 From: issues at jboss.org (Tom Ross (JIRA)) Date: Fri, 15 May 2015 11:20:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2412) XA transactions should be recoverable by any JBoss instance In-Reply-To: References: Message-ID: Tom Ross created JBTM-2412: ------------------------------ Summary: XA transactions should be recoverable by any JBoss instance Key: JBTM-2412 URL: https://issues.jboss.org/browse/JBTM-2412 Project: JBoss Transaction Manager Issue Type: Feature Request Components: Recovery Affects Versions: 5.1.1 Environment: JBoss EAP Reporter: Tom Ross Assignee: Tom Jenkinson At the moment when JBoss server crashes, the JBoss instance has to be restarted in order for the XA transactions to be recovered. It should be possible that after the crash any JBoss instance still running should be able to recover those transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 11:50:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 15 May 2015 11:50:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2413) narayana.sh fails on OS X In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2413: -------------------------------------- Summary: narayana.sh fails on OS X Key: JBTM-2413 URL: https://issues.jboss.org/browse/JBTM-2413 Project: JBoss Transaction Manager Issue Type: Bug Components: Build System Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.1.1 The build fails with: ./scripts/hudson/narayana.sh: line 640: free: command not found -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 15 13:41:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 15 May 2015 13:41:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2413) narayana.sh fails on OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2413: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/849 > narayana.sh fails on OS X > ------------------------- > > Key: JBTM-2413 > URL: https://issues.jboss.org/browse/JBTM-2413 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.1 > > > The build fails with: > ./scripts/hudson/narayana.sh: line 640: free: command not found -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 02:35:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 18 May 2015 02:35:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2412) XA transactions should be recoverable by any JBoss instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068661#comment-13068661 ] Tom Jenkinson commented on JBTM-2412: ------------------------------------- Hi Tom, Narayana can already do this actually do this. If I understand you correctly, I think what you are wanting is for EAP to provide this facility so you will need to raise this as an EAP feature request. Thanks, Tom > XA transactions should be recoverable by any JBoss instance > ----------------------------------------------------------- > > Key: JBTM-2412 > URL: https://issues.jboss.org/browse/JBTM-2412 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 5.1.1 > Environment: JBoss EAP > Reporter: Tom Ross > Assignee: Tom Jenkinson > > At the moment when JBoss server crashes, the JBoss instance has to be restarted in order for the XA transactions to be recovered. It should be possible that after the crash any JBoss instance still running should be able to recover those transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 02:36:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 18 May 2015 02:36:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2412) XA transactions should be recoverable by any JBoss instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson resolved JBTM-2412. --------------------------------- Resolution: Migrated to another ITS > XA transactions should be recoverable by any JBoss instance > ----------------------------------------------------------- > > Key: JBTM-2412 > URL: https://issues.jboss.org/browse/JBTM-2412 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 5.1.1 > Environment: JBoss EAP > Reporter: Tom Ross > Assignee: Tom Jenkinson > > At the moment when JBoss server crashes, the JBoss instance has to be restarted in order for the XA transactions to be recovered. It should be possible that after the crash any JBoss instance still running should be able to recover those transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 02:47:19 2015 From: issues at jboss.org (Tom Ross (JIRA)) Date: Mon, 18 May 2015 02:47:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2412) XA transactions should be recoverable by any JBoss instance In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068662#comment-13068662 ] Tom Ross commented on JBTM-2412: -------------------------------- Thanks Tom, Which component would that be. Tom > XA transactions should be recoverable by any JBoss instance > ----------------------------------------------------------- > > Key: JBTM-2412 > URL: https://issues.jboss.org/browse/JBTM-2412 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Recovery > Affects Versions: 5.1.1 > Environment: JBoss EAP > Reporter: Tom Ross > Assignee: Tom Jenkinson > > At the moment when JBoss server crashes, the JBoss instance has to be restarted in order for the XA transactions to be recovered. It should be possible that after the crash any JBoss instance still running should be able to recover those transactions. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 03:38:19 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 18 May 2015 03:38:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: Amos Feng created JBTM-2414: ------------------------------- Summary: Upgrade the version of wildfly to 10.0.0.Alpha2 Key: JBTM-2414 URL: https://issues.jboss.org/browse/JBTM-2414 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 03:50:19 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Mon, 18 May 2015 03:50:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amos Feng updated JBTM-2414: ---------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/851 > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 05:41:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 05:41:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2393) Add google analytics to the docs and narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2393: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add google analytics to the docs and narayana.io > ------------------------------------------------ > > Key: JBTM-2393 > URL: https://issues.jboss.org/browse/JBTM-2393 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Fix For: 5.next > > > For the docs, see an example here: > https://github.com/pressgang/pressgang-tools/blob/master/pressgang-tools-example/pom.xml#L79 > > UA-XXXXXXX-X > GTM-NJWS5L > MyProject > > We don't want that in normal builds, maybe add it in a release profile and update brp.xml to generate the docs with that enabled. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 05:41:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 05:41:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2375) Upload IDL and WSDL files to the web page In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2375: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upload IDL and WSDL files to the web page > ----------------------------------------- > > Key: JBTM-2375 > URL: https://issues.jboss.org/browse/JBTM-2375 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > Upload IDL and WSDL files to the web page, so that they would be easy to find. Also, update documentation to use the correct links. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 06:13:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 06:13:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2415) Clean documentation dependencies In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2415: ------------------------------------- Summary: Clean documentation dependencies Key: JBTM-2415 URL: https://issues.jboss.org/browse/JBTM-2415 Project: JBoss Transaction Manager Issue Type: Task Components: Documentation Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next There are many unused dependencies and plugins in documentation pom. Also, build-release-packages.xml file is out of date and not used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 06:20:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Mon, 18 May 2015 06:20:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2369: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/844, https://github.com/jbosstm/performance/pull/15 (was: https://github.com/jbosstm/narayana/pull/844) > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 07:14:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 07:14:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2415) Clean documentation dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2415: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/documentation/pull/32 > Clean documentation dependencies > -------------------------------- > > Key: JBTM-2415 > URL: https://issues.jboss.org/browse/JBTM-2415 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > There are many unused dependencies and plugins in documentation pom. > Also, build-release-packages.xml file is out of date and not used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 08:30:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 08:30:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris reassigned JBTM-1107: ------------------------------------- Assignee: Gytis Trikleris > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 08:30:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Mon, 18 May 2015 08:30:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-1107: ---------------------------------- Fix Version/s: 5.next (was: 6.later) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Task > Components: TXFramework > Reporter: Paul Robinson > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 08:52:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 18 May 2015 08:52:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2414: -------------------------------- Priority: Blocker (was: Major) > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Mon May 18 08:59:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Mon, 18 May 2015 08:59:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068813#comment-13068813 ] Tom Jenkinson commented on JBTM-2414: ------------------------------------- Hi Amos, I added a couple of comments on your PR as to what I found this morning but I will have to hand it back to you now. It looks like either arquillian or more likely EJB3 remoting inconsistency in WFLY is to blame. {code} WARN: The protocol 'http-remoting-jmx' is deprecated, instead you should use 'remote+http'. Exception in thread "Remoting "endpoint" task-4" java.lang.NoSuchMethodError: org.jboss.logging.Logger.tracef(Ljava/lang/String;I)V at org.jboss.remotingjmx.VersionedConectionFactory$ClientVersionReceiver.handleMessage(VersionedConectionFactory.java:158) at org.jboss.remoting3.remote.RemoteConnectionChannel$4.run(RemoteConnectionChannel.java:386) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} I can see that it is using tracef in master: https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jboss/remotingjmx/VersionedConectionFactory.java#L158 The thing is when I look in a built version of WFLY it has 3.2.1 in C:\Users\tom\projects\jbosstm\narayana\jboss-as\build\target\wildfly-10.0.0.Alpha2-SNAPSHOT\modules\system\layers\base\org\jboss\logging\main\module.xml and that is the version in the remoting-jmx pom.xml: https://github.com/jbossas/remoting-jmx/blob/master/pom.xml#L154 I think its possible an older incompatible version of jboss-logging could be in the test.war but I can't seem to get Arquillian to leave the war behind to check that out... Tom > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 04:06:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 04:06:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove reopened JBTM-2369: ------------------------------------ I provided a script to collect the hardware details which is run by the jenkins job config. It would be preferable for this to controlled via the part of the narayana.sh script which runs the benchmark. > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 04:29:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 May 2015 04:29:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2406: ---------------------------------- Summary: BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition (was: BAParticipantCompletionTest test failed because of the race condition) > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 04:34:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 May 2015 04:34:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2416: ------------------------------------- Summary: OSGiJTATest #testTransactionManager failed Key: JBTM-2416 URL: https://issues.jboss.org/browse/JBTM-2416 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Reporter: Gytis Trikleris Assignee: Michael Musgrove Priority: Minor Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console {code} Running org.jboss.narayana.osgi.jta.OSGiJTATest Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 04:56:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 May 2015 04:56:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Comment: was deleted (was: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/757/PROFILE=XTS,jdk=jdk7.latest,label=linux/) > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 04:57:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 May 2015 04:57:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2194) Activity cancelled by coordinator in CloseTest In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2194: ---------------------------------- Comment: was deleted (was: Happened again on CI: http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/723/PROFILE=XTS,jdk=jdk7.latest,label=linux) > Activity cancelled by coordinator in CloseTest > ---------------------------------------------- > > Key: JBTM-2194 > URL: https://issues.jboss.org/browse/JBTM-2194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > > {code} > ------------------------------------------------------------------------------- > Test set: com.arjuna.wstx.tests.arq.ba.CloseTest > ------------------------------------------------------------------------------- > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.866 sec <<< FAILURE! > testClose(com.arjuna.wstx.tests.arq.ba.CloseTest) Time elapsed: 2.375 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at com.arjuna.wstx.tests.arq.ba.CloseTest.testClose(CloseTest.java:64) > {code} > {code} > 18:45:37,613 INFO [org.jboss.as.repository] (management-handler-thread - 8) WFLYDR0001: Content added at location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:37,616 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "test.war" (runtime-name: "test.war") > 18:45:37,860 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.test.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice. > 18:45:37,927 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Processing weld deployment test.war > 18:45:37,941 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Starting Services for CDI deployment: test.war > 18:45:37,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment test.war > 18:45:38,228 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: /test > 18:45:38,406 INFO [org.jboss.as.server] (management-handler-thread - 8) WFLYSRV0010: Deployed "test.war" (runtime-name : "test.war") > 18:45:38,418 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:38,492 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,492 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,493 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,495 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,496 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules.setParticipantCount(java.lang.Integer) void for rule create counter > 18:45:38,497 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for create counter in class org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:38,514 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,517 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine.completed(org.oasis_open.docs.ws_tx.wsba._2006._06.NotificationType,org.jboss.ws.api.addressing.MAP,com.arjuna.webservices11.wsarj.ArjunaContext) void for rule complete called > 18:45:38,536 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for complete called in class com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:38,552 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,554 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.cancelOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule cancel called > 18:45:38,556 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for cancel called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,558 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : possible trigger for rule close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:38,559 INFO [stdout] (Thread-0) RuleTriggerMethodAdapter.injectTriggerPoint : inserting trigger into com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl.closeOperation(com.arjuna.schemas.ws._2005._10.wsarjtx.NotificationType) void for rule close called > 18:45:38,560 INFO [stdout] (Thread-0) org.jboss.byteman.agent.Transformer : inserted trigger for close called in class com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:39,123 INFO [stdout] (default task-16) Rule.execute called for create counter_3 > 18:45:39,124 INFO [stdout] (default task-16) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) calling activated() for helper class org.jboss.byteman.rule.helper.Helper > 18:45:39,124 INFO [stdout] (default task-16) Default helper activated > 18:45:39,124 INFO [stdout] (default task-16) calling installed(create counter) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:39,125 INFO [stdout] (default task-16) Installed rule using default helper : create counter > 18:45:39,135 INFO [stdout] (default task-16) create counter execute > 18:45:39,135 INFO [stdout] (default task-16) rule.debug{create counter} : participant_completion.counter.create: 1 > 18:45:39,158 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,205 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}ActivationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-activation-binding.wsdl > 18:45:39,282 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:40,131 WARN [com.arjuna.wst] (default task-16) ARJUNA043225: Could not save recovery state for non-serializable WS-BA participant 1235 > 18:45:40,188 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:41,372 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (Timer-1) Creating Service {http://docs.oasis-open.org/ws-tx/wsba/2006/06}BusinessAgreementWithParticipantCompletionCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wsba/_2006/_06/wsdl/wsba-participant-completion-coordinator-binding.wsdl > 18:45:42,052 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegistrationService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/org/oasis_open/docs/ws_tx/wscoor/_2006/_06/wsdl/wscoor-registration-binding.wsdl > 18:45:42,090 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (default task-16) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationCoordinatorService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-coordinator-binding.wsdl > 18:45:42,409 INFO [stdout] (default-workqueue-2) Rule.execute called for close called_6 > 18:45:42,410 INFO [stdout] (default-workqueue-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) calling installed(close called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,411 INFO [stdout] (default-workqueue-2) Installed rule using default helper : close called > 18:45:42,411 INFO [stdout] (default-workqueue-2) close called execute > 18:45:42,412 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.waiting > 18:45:42,412 INFO [stdout] (TaskWorker-2) Rule.execute called for complete called_4 > 18:45:42,413 INFO [stdout] (TaskWorker-2) HelperManager.install for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) calling installed(complete called) for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,413 INFO [stdout] (TaskWorker-2) Installed rule using default helper : complete called > 18:45:42,413 INFO [stdout] (TaskWorker-2) complete called execute > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.counter.decrement > 18:45:42,414 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.waking > 18:45:42,414 INFO [stdout] (default-workqueue-2) rule.debug{close called} : participant_completion.close.woken > 18:45:42,415 INFO [stdout] (TaskWorker-2) rule.debug{complete called} : participant_completion.called.donewake > 18:45:42,415 WARN [com.arjuna.mw.wstx] (TaskWorker-2) ARJUNA045062: Coordinator cancelled the activity > 18:45:42,428 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (TaskWorker-2) Creating Service {http://schemas.arjuna.com/ws/2005/10/wsarjtx}TerminationParticipantService from WSDL: jar:file:/home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/jboss/xts/main/jbossxts-5.0.3.Final-SNAPSHOT.jar!/com/arjuna/schemas/ws/_2005/_10/wsarjtx/wsdl/wsarjtx-termination-participant-binding.wsdl > 18:45:42,439 INFO [stdout] (TaskWorker-1) Rule.execute called for complete called_4 > 18:45:42,441 INFO [stdout] (TaskWorker-1) complete called execute > 18:45:42,496 INFO [stdout] (Thread-0) TransformListener() : handling connection on port 9091 > 18:45:42,598 INFO [stdout] (Thread-0) retransforming org.jboss.jbossts.xts.bytemanSupport.participantCompletion.ParticipantCompletionCoordinatorRules > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine > 18:45:42,599 INFO [stdout] (Thread-0) retransforming com.arjuna.webservices11.wsarjtx.sei.TerminationCoordinatorPortTypeImpl > 18:45:42,815 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) calling uninstalled(create counter) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,816 INFO [stdout] (Thread-0) Uninstalled rule using default helper : create counter > 18:45:42,817 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,817 INFO [stdout] (Thread-0) calling uninstalled(complete called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,818 INFO [stdout] (Thread-0) Uninstalled rule using default helper : complete called > 18:45:42,818 INFO [stdout] (Thread-0) HelperManager.uninstall for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) calling uninstalled(close called) for helper class org.jboss.byteman.rule.helper.Helper > 18:45:42,819 INFO [stdout] (Thread-0) Uninstalled rule using default helper : close called > 18:45:42,819 INFO [stdout] (Thread-0) calling deactivated() for helper classorg.jboss.byteman.rule.helper.Helper > 18:45:42,820 INFO [stdout] (Thread-0) Default helper deactivated > 18:45:42,830 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0022: Unregistered web context: /test > 18:45:42,845 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Stopping weld service for deployment test.war > 18:45:42,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment test.war (runtime-name: test.war) in 26ms > 18:45:42,942 INFO [org.jboss.as.repository] (management-handler-thread - 7) WFLYDR0002: Content removed from location /home/hudson/workspace/narayana/PROFILE/XTS/jdk/jdk7.latest/label/linux/jboss-as/build/target/wildfly-9.0.0.Alpha1-SNAPSHOT/standalone/data/content/2a/0685005c0b26622b16a38150f088bad88f5ed8/content > 18:45:42,942 INFO [org.jboss.as.server] (management-handler-thread - 7) WFLYSRV0009: Undeployed "test.war" (runtime-name: "test.war") >  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 05:07:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Tue, 19 May 2015 05:07:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson reassigned JBTM-2416: ----------------------------------- Assignee: Amos Feng (was: Michael Musgrove) > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 05:23:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Tue, 19 May 2015 05:23:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2417) Create CI pull request job for narayana.io In-Reply-To: References: Message-ID: Gytis Trikleris created JBTM-2417: ------------------------------------- Summary: Create CI pull request job for narayana.io Key: JBTM-2417 URL: https://issues.jboss.org/browse/JBTM-2417 Project: JBoss Transaction Manager Issue Type: Task Components: Build System, Documentation Reporter: Gytis Trikleris Assignee: Gytis Trikleris Fix For: 5.next -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 06:33:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 06:33:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2369: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/844, https://github.com/jbosstm/performance/pull/15, https://github.com/jbosstm/narayana/pull/850 (was: https://github.com/jbosstm/narayana/pull/844, https://github.com/jbosstm/performance/pull/15) > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 06:45:21 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 06:45:21 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2413) narayana.sh fails on OS X In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove closed JBTM-2413. ---------------------------------- Resolution: Duplicate Issue I fixed this in JBTM-2369 > narayana.sh fails on OS X > ------------------------- > > Key: JBTM-2413 > URL: https://issues.jboss.org/browse/JBTM-2413 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.1.1 > > > The build fails with: > ./scripts/hudson/narayana.sh: line 640: free: command not found -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 06:47:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 06:47:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2369) Include output of the hardware used when reporting benchmark results In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove resolved JBTM-2369. ------------------------------------ Resolution: Done > Include output of the hardware used when reporting benchmark results > -------------------------------------------------------------------- > > Key: JBTM-2369 > URL: https://issues.jboss.org/browse/JBTM-2369 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Performance Testing > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > > Anything we can get from the OS would be useful. If we can't get vendor and spec automatically we will need to identify these manually and maybe have a document somewhere that we can link to in the results. > e.g. ran on haverstraw, haverstraw spec is http://narayana.io/perfmachinespecs/haverstraw.html > Or something like that. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 07:51:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 07:51:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2403) Add a quickstart for Undertow + REST-AT + JAX-RS In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2403: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add a quickstart for Undertow + REST-AT + JAX-RS > ------------------------------------------------ > > Key: JBTM-2403 > URL: https://issues.jboss.org/browse/JBTM-2403 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Undertow + REST-AT + JAX-RS is a good simple showcase of our projects. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 11:44:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 11:44:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2414: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/851, https://github.com/jbosstm/narayana/pull/852 (was: https://github.com/jbosstm/narayana/pull/851) > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 19 11:47:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 19 May 2015 11:47:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069335#comment-13069335 ] Michael Musgrove commented on JBTM-2414: ---------------------------------------- Amos, I have applied a workaround by not upgrading version.org.wildfly.arquillian from 1.0.0.Alpha5 If your PR passes then please overlay your changes on mine. > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 03:22:20 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 20 May 2015 03:22:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069454#comment-13069454 ] Amos Feng commented on JBTM-2414: --------------------------------- Thanks Mike, I have updated the PR to upgrade the other artifacts. > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 03:26:19 2015 From: issues at jboss.org (Amos Feng (JIRA)) Date: Wed, 20 May 2015 03:26:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069456#comment-13069456 ] Amos Feng commented on JBTM-2416: --------------------------------- It looks like the arquillian-container-karaf-embedded 2.1.0.CR15 only works with arquillian-core 1.1.2.Final > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 04:23:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 04:23:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2416) OSGiJTATest #testTransactionManager failed In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069470#comment-13069470 ] Tom Jenkinson commented on JBTM-2416: ------------------------------------- Is there an upgrade for arquillian-container-karaf-embedded? > OSGiJTATest #testTransactionManager failed > ------------------------------------------ > > Key: JBTM-2416 > URL: https://issues.jboss.org/browse/JBTM-2416 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Reporter: Gytis Trikleris > Assignee: Amos Feng > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/837/PROFILE=MAIN,jdk=jdk8.latest,label=linux/console > {code} > Running org.jboss.narayana.osgi.jta.OSGiJTATest > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 17.09 sec <<< FAILURE! > testTransactionManager(org.jboss.narayana.osgi.jta.OSGiJTATest) Time elapsed: 0.003 sec <<< FAILURE! > java.lang.AssertionError: Bundle ACTIVE expected:<32> but was:<4> > at org.junit.Assert.fail(Assert.java:88) > at org.junit.Assert.failNotEquals(Assert.java:743) > at org.junit.Assert.assertEquals(Assert.java:118) > at org.junit.Assert.assertEquals(Assert.java:555) > at org.jboss.narayana.osgi.jta.OSGiJTATest.testTransactionManager(OSGiJTATest.java:81) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 05:20:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 20 May 2015 05:20:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2418) NPE in BaseTransactionManagerDelegate commit In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2418: -------------------------------------- Summary: NPE in BaseTransactionManagerDelegate commit Key: JBTM-2418 URL: https://issues.jboss.org/browse/JBTM-2418 Project: JBoss Transaction Manager Issue Type: Bug Components: Application Server Integration Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next BaseTransactionManagerDelegate#commit should throw IllegalStateException if there is no transaction present. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 05:55:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 20 May 2015 05:55:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2419) Consider reducing the number of JMH perf test forks on PRs In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2419: -------------------------------------- Summary: Consider reducing the number of JMH perf test forks on PRs Key: JBTM-2419 URL: https://issues.jboss.org/browse/JBTM-2419 Project: JBoss Transaction Manager Issue Type: Task Components: Testing Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later We run our JMH tests multiple times in order to estimate run-to-run variance. The [JMH docs|http://hg.openjdk.java.net/code-tools/jmh/file/tip/jmh-samples/src/main/java/org/openjdk/jmh/samples/JMHSample_13_RunToRun.java] state: bq. JVMs are complex systems, and the non-determinism is inherent for them. This requires us to always account the run-to-run variance as the one of the effects in our experiments. Forking aggregates the results across several JVM launches. Currently we set the number of forks to 10. We run each test 6 times with each run lasting 1 min. Since we have 10 tests this means it takes 10 * 10 * 6 minutes for the benchmarks to complete. In the future we want to keep adding new performance tests and the time taken to run a PR will become prohibitive. I would like to propose one of the following solutions: - reduce the number of forks; - run a subset of performance tests on each PR and then run them all once a week or so on the main build My preference is to reduce the number of forks to 3. Note that the PR requester has the option to disable performance tests for his PR (by including !PERF in the comment section). -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 06:17:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 20 May 2015 06:17:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2414: ----------------------------------- Yesterday I pushed the fix that does not upgrade arquillian so we are good to go on our CI builds. Do you think the jira still warrants the blocker status? Mike -- Michael Musgrove Red Hat UK Ltd, Transactions Team e: mmusgrov at redhat.com t: +44 191 243 0870 Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US), Michael O'Neill(Ireland) > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 07:00:24 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 20 May 2015 07:00:24 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2415) Clean documentation dependencies In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2415: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Clean documentation dependencies > -------------------------------- > > Key: JBTM-2415 > URL: https://issues.jboss.org/browse/JBTM-2415 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > There are many unused dependencies and plugins in documentation pom. > Also, build-release-packages.xml file is out of date and not used. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 07:42:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 20 May 2015 07:42:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2418) NPE in BaseTransactionManagerDelegate commit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2418: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/853 > NPE in BaseTransactionManagerDelegate commit > -------------------------------------------- > > Key: JBTM-2418 > URL: https://issues.jboss.org/browse/JBTM-2418 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > BaseTransactionManagerDelegate#commit should throw IllegalStateException if there is no transaction present. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:03:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:03:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2414: -------------------------------- Priority: Major (was: Blocker) > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:03:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:03:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2414) Upgrade the version of wildfly to 10.0.0.Alpha2 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13069555#comment-13069555 ] Tom Jenkinson commented on JBTM-2414: ------------------------------------- Agreed - reverting to default status. > Upgrade the version of wildfly to 10.0.0.Alpha2 > ----------------------------------------------- > > Key: JBTM-2414 > URL: https://issues.jboss.org/browse/JBTM-2414 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:53:20 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:53:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2420) BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2420: ----------------------------------- Summary: BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) Key: JBTM-2420 URL: https://issues.jboss.org/browse/JBTM-2420 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie, REST Reporter: Tom Jenkinson Assignee: Amos Feng Priority: Blocker Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/918/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:56:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:56:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2295) Expose REST-TX (and WS-TX) endpoints through Docker In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2295: -------------------------------- Issue Type: Task (was: Feature Request) > Expose REST-TX (and WS-TX) endpoints through Docker > --------------------------------------------------- > > Key: JBTM-2295 > URL: https://issues.jboss.org/browse/JBTM-2295 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Cloud, REST, XTS > Affects Versions: 5.0.3 > Reporter: Mark Little > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:57:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:57:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2397) Update pom.xml for JDK8 compatability with findbugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2397: -------------------------------- Summary: Update pom.xml for JDK8 compatability with findbugs (was: Update jboss-parent to allow building with required JDK8 updates such as findbugs) > Update pom.xml for JDK8 compatability with findbugs > --------------------------------------------------- > > Key: JBTM-2397 > URL: https://issues.jboss.org/browse/JBTM-2397 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Current version of parent is 17 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:57:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:57:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2397) Update pom.xml for JDK8 compatability with findbugs In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2397: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update pom.xml for JDK8 compatability with findbugs > --------------------------------------------------- > > Key: JBTM-2397 > URL: https://issues.jboss.org/browse/JBTM-2397 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Current version of parent is 17 -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:58:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:58:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2395) Correct Javadoc errors on JDK8 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2395: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Correct Javadoc errors on JDK8 > ------------------------------ > > Key: JBTM-2395 > URL: https://issues.jboss.org/browse/JBTM-2395 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > WFLY has updated to JDK8, this means due to our build approach (early integration testing and BlackTie) we need to make sure we are compatible with JDK8. Currently there are Javadoc errors. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 08:58:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Wed, 20 May 2015 08:58:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2405) QA suite test failure: CrashRecovery05_1 Test04 In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2405: -------------------------------- Fix Version/s: 5.later (was: 5.next) > QA suite test failure: CrashRecovery05_1 Test04 > ----------------------------------------------- > > Key: JBTM-2405 > URL: https://issues.jboss.org/browse/JBTM-2405 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.later > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/830/PROFILE=QA_JTS_JACORB,jdk=jdk8.latest,label=linux/ -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 09:13:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 20 May 2015 09:13:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2406: ---------------------------------- Fix Version/s: 5.next (was: 5.later) > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 09:13:20 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 20 May 2015 09:13:20 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2406: ---------------------------------- Priority: Major (was: Minor) > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 20 09:20:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Wed, 20 May 2015 09:20:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2406: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/854/files > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 03:17:19 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 21 May 2015 03:17:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2418) NPE in BaseTransactionManagerDelegate commit In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2418: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > NPE in BaseTransactionManagerDelegate commit > -------------------------------------------- > > Key: JBTM-2418 > URL: https://issues.jboss.org/browse/JBTM-2418 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Application Server Integration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > BaseTransactionManagerDelegate#commit should throw IllegalStateException if there is no transaction present. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 04:44:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 21 May 2015 04:44:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2406) BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gytis Trikleris updated JBTM-2406: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BABridgedTest and BAParticipantCompletionTest tests failed because of the race condition > ---------------------------------------------------------------------------------------- > > Key: JBTM-2406 > URL: https://issues.jboss.org/browse/JBTM-2406 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TXFramework > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Status/job/narayana/825/PROFILE=XTS,jdk=jdk7.latest,label=linux/ > {code} > ------------------------------------------------------------------------------- > Test set: org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest > ------------------------------------------------------------------------------- > Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 44.774 sec <<< FAILURE! > testManualComplete(org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest) Time elapsed: 4.202 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.BusinessActivityTerminatorStub.close(BusinessActivityTerminatorStub.java:95) > at com.arjuna.mwlabs.wst11.ba.remote.UserBusinessActivityImple.close(UserBusinessActivityImple.java:157) > at org.jboss.narayana.txframework.functional.ws.ba.participantCompletion.BAParticipantCompletionTest.testManualComplete(BAParticipantCompletionTest.java:129) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 09:55:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 21 May 2015 09:55:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2420) BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070042#comment-13070042 ] Tom Jenkinson commented on JBTM-2420: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-quickstarts-catelyn/791/console > BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2420 > URL: https://issues.jboss.org/browse/JBTM-2420 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/918/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 12:06:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 21 May 2015 12:06:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2421) Provide some quickstarts for STM In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2421: ----------------------------------- Summary: Provide some quickstarts for STM Key: JBTM-2421 URL: https://issues.jboss.org/browse/JBTM-2421 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator, STM Reporter: Tom Jenkinson Assignee: Tom Jenkinson Fix For: 5.next As part of my JBug I took the example from the documentation and produced a set of quickstarts that would be useful to contribute to the project. The examples show: 1. Pessimistic locking 2. Optimistic locking 3. Use of an STM object in a JTA transaction -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 12:07:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Thu, 21 May 2015 12:07:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2421) Provide some quickstarts for STM In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Jenkinson updated JBTM-2421: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/140 > Provide some quickstarts for STM > -------------------------------- > > Key: JBTM-2421 > URL: https://issues.jboss.org/browse/JBTM-2421 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, STM > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > As part of my JBug I took the example from the documentation and produced a set of quickstarts that would be useful to contribute to the project. > The examples show: > 1. Pessimistic locking > 2. Optimistic locking > 3. Use of an STM object in a JTA transaction -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 21 12:18:19 2015 From: issues at jboss.org (Gytis Trikleris (JIRA)) Date: Thu, 21 May 2015 12:18:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2417) Create CI pull request job for narayana.io In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070117#comment-13070117 ] Gytis Trikleris commented on JBTM-2417: --------------------------------------- I have this partially working. However, it might be good to update a web page in a way that it would work simply by opening index.html. Now, for example navigation will not work in such case. [~tomjenkinson], take a look under _site once you're on NCL VPN: http://172.17.130.4:8083/job/btny-pulls-narayana-io/jdk=jdk8.latest,label=linux/14/ > Create CI pull request job for narayana.io > ------------------------------------------ > > Key: JBTM-2417 > URL: https://issues.jboss.org/browse/JBTM-2417 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, Documentation > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 22 04:54:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 22 May 2015 04:54:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2420) BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070283#comment-13070283 ] Tom Jenkinson commented on JBTM-2420: ------------------------------------- http://albany.eng.hst.ams2.redhat.com/job/narayana-catelyn/920/ > BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2420 > URL: https://issues.jboss.org/browse/JBTM-2420 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/918/consoleFull -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 22 07:33:19 2015 From: issues at jboss.org (Tom Jenkinson (JIRA)) Date: Fri, 22 May 2015 07:33:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2422) Consider @Optimistic/@Pessimistic annotations on the Container In-Reply-To: References: Message-ID: Tom Jenkinson created JBTM-2422: ----------------------------------- Summary: Consider @Optimistic/@Pessimistic annotations on the Container Key: JBTM-2422 URL: https://issues.jboss.org/browse/JBTM-2422 Project: JBoss Transaction Manager Issue Type: Enhancement Components: STM Reporter: Tom Jenkinson Assignee: Mark Little Would it make sense for the container to be optionally marked as @Optimistic and @Pessimistic thereby allowing an override of the behaviour requested by the object. The scenario I am considering is if you imagine a library of STM objects developed by some other team, could it be that the concurrency control of them is best defined by the app and the easiest way to do that might be via Container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 22 10:16:19 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Fri, 22 May 2015 10:16:19 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2422) Consider @Optimistic/@Pessimistic annotations on the Container In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070440#comment-13070440 ] Mark Little commented on JBTM-2422: ----------------------------------- So the reason I haven't allowed this is because the semantics of the class/object and associated application may change dramatically between pessimistic and optimistic. The developer needs to understand the differences and someone who created their classes using optimistic, say, may not be the person who then uses them within a container years later that tries to override this annotation. I'd thought of allowing some annotations on classes/interfaces to override those of the container or vice versa in general, i.e., not just specifically for optimistic or pessimistic. For some it does make sense. For others not so much. Obviously we could control this within the annotation itself by saying whether or not it allows being overridden. > Consider @Optimistic/@Pessimistic annotations on the Container > -------------------------------------------------------------- > > Key: JBTM-2422 > URL: https://issues.jboss.org/browse/JBTM-2422 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: STM > Reporter: Tom Jenkinson > Assignee: Mark Little > > Would it make sense for the container to be optionally marked as @Optimistic and @Pessimistic thereby allowing an override of the behaviour requested by the object. The scenario I am considering is if you imagine a library of STM objects developed by some other team, could it be that the concurrency control of them is best defined by the app and the easiest way to do that might be via Container. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Tue May 26 11:49:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Tue, 26 May 2015 11:49:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2423: -------------------------------------- Summary: ORBRunner uses the orb after run() returns Key: JBTM-2423 URL: https://issues.jboss.org/browse/JBTM-2423 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Michael Musgrove Assignee: Michael Musgrove ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: {quote} Once an ORB has shutdown, only object reference management operations(duplicate, release and is_nil) may be invoked on the ORB or any object reference obtained from it. {quote} Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: {quote} This operation will block until the ORB has completed the shutdown process, {quote} This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held # at this point the jdk orb shutdown would normally then return allowing the the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Wed May 27 10:07:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Wed, 27 May 2015 10:07:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071563#comment-13071563 ] Michael Musgrove commented on JBTM-1339: ---------------------------------------- wildfly is now running JTS just fine with the openjdk orb. To use it standalone (ie outside of JBoss Modules) we need to prepend the openjdk jar to the bootclasspath. I tried that on the jtax tests (via surefire argLine) and the tests run fine. My plan is to add another maven profile to run the surefire tests against openjdk-orb but the default will still be to use whatever comes with rt.jar > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 28 08:40:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 May 2015 08:40:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/855 > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 28 09:34:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 May 2015 09:34:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071944#comment-13071944 ] Michael Musgrove commented on JBTM-2423: ---------------------------------------- An example of the deadlock is in one of our unit tests (ResourceManagerFailureUnitTest) where thread "main" takes the monitor 0x000000076ea03ba0 in shudown. The code inside the openjdk-orb library then notfies "Thread-2" and then joins with it. But "Thread-2" is blocked on the same monitor because it illegally tries to access the orb after the run loop finishes: {code} Full thread dump Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode): "Thread-2" #12 daemon prio=5 os_prio=0 tid=0x00007fc5c8640000 nid=0x390d waiting for monitor entry [0x00007fc599cb9000] java.lang.Thread.State: BLOCKED (on object monitor) at com.arjuna.orbportability.ORB.shutdown(ORB.java:252) - waiting to lock <0x000000076ea03ba0> (a com.arjuna.orbportability.ORB) at com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.ORBRunner.run(ORBRunner.java:62) "main" #1 prio=5 os_prio=0 tid=0x00007fc5c8008800 nid=0x38f9 in Object.wait() [0x00007fc5cf022000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on <0x000000076f26a3c0> (a com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.ORBRunner) at java.lang.Thread.join(Thread.java:1245) - locked <0x000000076f26a3c0> (a com.arjuna.ats.internal.jts.orbspecific.javaidl.recoverycoordinators.ORBRunner) at java.lang.Thread.join(Thread.java:1319) at com.sun.corba.se.impl.orb.ORBImpl.shutdown(ORBImpl.java:1310) - locked <0x000000076ede1c68> (a java.lang.Object) at com.arjuna.orbportability.internal.orbspecific.orb.implementations.ORBBase.shutdown(ORBBase.java:93) - locked <0x000000076eb14828> (a com.arjuna.orbportability.internal.orbspecific.javaidl.orb.implementations.javaidl_1_4) at com.arjuna.orbportability.orb.core.ORB.shutdown(ORB.java:95) at com.arjuna.orbportability.ORB.shutdown(ORB.java:295) - locked <0x000000076ea03ba0> (a com.arjuna.orbportability.ORB) at com.arjuna.orbportability.ORB.shutdown(ORB.java:252) - locked <0x000000076ea03ba0> (a com.arjuna.orbportability.ORB) at com.hp.mwtests.ts.jta.jts.recovery.ResourceManagerFailureUnitTest.after(ResourceManagerFailureUnitTest.java:94) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) at org.junit.runners.ParentRunner.run(ParentRunner.java:309) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:159) at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:87) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:95) > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 28 09:35:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 May 2015 09:35:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2423: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/855 > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 28 10:20:02 2015 From: issues at jboss.org (Mark Little (JIRA)) Date: Thu, 28 May 2015 10:20:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071967#comment-13071967 ] Mark Little commented on JBTM-2423: ----------------------------------- In the change you've removed ... try - { - if (JavaIdlRCServiceInit._oa != null) - JavaIdlRCServiceInit._oa.destroy(); - - if (JavaIdlRCServiceInit._orb != null) - JavaIdlRCServiceInit._orb.shutdown(); - } - catch (Exception ex) - { - } Have you checked through the code paths to make sure we're not relying on OA destroy or ORB shutdown to do trigger something else? > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Thu May 28 12:41:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Thu, 28 May 2015 12:41:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072019#comment-13072019 ] Michael Musgrove commented on JBTM-2423: ---------------------------------------- Since the run loop for JavaIdlRCServiceInit._orb has finished some code somewhere must have already called shutdown on it. The spec says that shutdown calls destroy on the root poa which in turn calls shutdown on its immediate descendants. So when the run loop finishes the code I have removed should effectively already have been called (ie both the shutdown on the orb and the destroy on the object adaptor). The relevant bits of the spec I refer to are 4.2.5.4 shutdown {quote} Additionally in systems that have Portable Object Adapters (see Chapter 11) shutdown behaves as if POA::destroy is called on the Root POA with its first parameter set to TRUE and the second parameter set to the value of the wait_for_completion parameter that shutdown is invoked with. {quote} and {quote} And POA::destroy will call destroy on all of its immediate descendants. {quote} > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 04:49:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 04:49:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072161#comment-13072161 ] Michael Musgrove commented on JBTM-2423: ---------------------------------------- Mark, you are correct. We are calling destroy on our own wrapper which does indeed do some extra work. I will revisit the fix, thanks. > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 07:22:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 07:22:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072214#comment-13072214 ] Michael Musgrove commented on JBTM-2423: ---------------------------------------- I added a line in orbportability/ORB.java to ensure that destroy is/has already been called on our root poa wrapper. This means that if whoever called shutdown on our ORB wrapper forgets to explicitly destroy it then we will do so guaranteeing that our pre/post poa destroy hooks get invoked. > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 09:39:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 09:39:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2423: ----------------------------------- Fix Version/s: 5.next > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 09:41:03 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 09:41:03 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2423) ORBRunner uses the orb after run() returns In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2423: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done The fix will be available in the next narayana 5.1.x release. If it needs back porting then we will need to create a 5.0.6 release. > ORBRunner uses the orb after run() returns > ------------------------------------------ > > Key: JBTM-2423 > URL: https://issues.jboss.org/browse/JBTM-2423 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > ORBRunner.java starts an orb using orb().run() but then performs operations on the orb after the run() method returns. According to the CORBA spec this is invalid: > {quote} > Once an ORB has shutdown, only object reference management operations(duplicate, > release and is_nil) may be invoked on the ORB or any object reference obtained > from it. > {quote} > Note that when the orb.run() method returns the orb has shutdown because, for the run method, the spec states: > {quote} > This operation will block until the ORB has completed the shutdown process, > {quote} > This issue has arisen because of a change made to our fork of the jdk orb: in the jdk orb shutdown method we join with all the orb runners. This results in deadlock: > # com.arjuna.orbportability.ORB.shutdown is a synchronized method and it calls shutdown on the jdk orb; > # shutdown on the jdk orb notifies the ORBRunner thread which now tries to call back into a synchronized method of com.arjuna.orbportability.ORB but is blocked because the monitor is held > # at this point the jdk orb shutdown would normally then return allowing the > the ORBRunner thread to make progress but a recent change now means that the jdk orb shutdown method performs a join() on the various ORBRunner threads -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 09:44:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 09:44:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-1339) Ensure that JTS can use the JDK ORB provided by WildFly In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-1339: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Support for this ORB can be tested by passing the following flags to the build: {code} -Djacorb-disabled -Didlj-disabled {code} > Ensure that JTS can use the JDK ORB provided by WildFly > ------------------------------------------------------- > > Key: JBTM-1339 > URL: https://issues.jboss.org/browse/JBTM-1339 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Fri May 29 11:11:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Fri, 29 May 2015 11:11:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2424) Change hornetq dependency to the journal only In-Reply-To: References: Message-ID: Michael Musgrove created JBTM-2424: -------------------------------------- Summary: Change hornetq dependency to the journal only Key: JBTM-2424 URL: https://issues.jboss.org/browse/JBTM-2424 Project: JBoss Transaction Manager Issue Type: Task Components: Transaction Core Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.next Currently we depend on hornetq-core. The later releases provide a hornetq-journal artifact that we use instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat May 30 16:33:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 30 May 2015 16:33:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2424) Change hornetq dependency to the journal only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2424: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/856 > Change hornetq dependency to the journal only > --------------------------------------------- > > Key: JBTM-2424 > URL: https://issues.jboss.org/browse/JBTM-2424 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we depend on hornetq-core. The later releases provide a hornetq-journal artifact that we use instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346) From issues at jboss.org Sat May 30 16:34:02 2015 From: issues at jboss.org (Michael Musgrove (JIRA)) Date: Sat, 30 May 2015 16:34:02 -0400 (EDT) Subject: [jbossts-issues] [JBoss JIRA] (JBTM-2424) Change hornetq dependency to the journal only In-Reply-To: References: Message-ID: [ https://issues.jboss.org/browse/JBTM-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Musgrove updated JBTM-2424: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Change hornetq dependency to the journal only > --------------------------------------------- > > Key: JBTM-2424 > URL: https://issues.jboss.org/browse/JBTM-2424 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Transaction Core > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Currently we depend on hornetq-core. The later releases provide a hornetq-journal artifact that we use instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)