[JBoss JIRA] (JBTM-2946) LRA quickstart is not spec compliant
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2946?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2946:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LRA quickstart is not spec compliant
> ------------------------------------
>
> Key: JBTM-2946
> URL: https://issues.jboss.org/browse/JBTM-2946
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.7.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
>
> The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
> The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
> In particular look at the code TripCheck.java in commit e2514c4bb3e2b80f0
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2947) LRA client API is still using the old spec
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2947?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2947:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LRA client API is still using the old spec
> ------------------------------------------
>
> Key: JBTM-2947
> URL: https://issues.jboss.org/browse/JBTM-2947
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.7.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
>
> The LRA end call in the client API is still expecting the response to contain are array of strings returned by each participant during the termination phase. The spec has since been updated and instead just the current status of the LRA is returned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2947) LRA client API is still using the old spec
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2947?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Michael Musgrove created pull request #1232 in GitHub
-----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> LRA client API is still using the old spec
> ------------------------------------------
>
> Key: JBTM-2947
> URL: https://issues.jboss.org/browse/JBTM-2947
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.7.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
>
> The LRA end call in the client API is still expecting the response to contain are array of strings returned by each participant during the termination phase. The spec has since been updated and instead just the current status of the LRA is returned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2932) LRA Cdi REST integration test hang
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2932?page=com.atlassian.jira.plugin.... ]
Michael Musgrove closed JBTM-2932.
----------------------------------
Resolution: Cannot Reproduce Bug
This issue is no longer present so closing as cannot reproduce.
> LRA Cdi REST integration test hang
> ----------------------------------
>
> Key: JBTM-2932
> URL: https://issues.jboss.org/browse/JBTM-2932
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.6.4.Final
> Reporter: Michael Musgrove
> Assignee: Ondra Chaloupka
>
> The test is hanging. Swarm boots fine but it then just waits (forever):
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running io.narayana.lra.cdi.StartCdiCheckIT
> Tue Sep 19 10:29:53 BST 2017 INFO [org.wildfly.swarm.bootstrap] (main) Dependencies not bundled; resolving from M2REPO.
> [0m2017-09-19 10:29:55,627 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Logging - STABLE org.wildfly.swarm:logging:2017.8.1
> [0m[0m2017-09-19 10:29:55,676 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Bean Validation - STABLE org.wildfly.swarm:bean-validation:2017.8.1
> [0m[0m2017-09-19 10:29:55,677 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: CDI Configuration - STABLE org.wildfly.swarm:cdi-config:2017.8.1
> [0m[0m2017-09-19 10:29:55,677 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Transactions - STABLE org.wildfly.swarm:transactions:2017.8.1
> [0m[0m2017-09-19 10:29:55,678 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: CDI - STABLE org.wildfly.swarm:cdi:2017.8.1
> [0m[0m2017-09-19 10:29:55,679 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: Undertow - STABLE org.wildfly.swarm:undertow:2017.8.1
> [0m[0m2017-09-19 10:29:55,679 INFO [org.wildfly.swarm] (main) WFSWARM0013: Installed fraction: JAX-RS - STABLE org.wildfly.swarm:jaxrs:2017.8.1
> [0m[0m2017-09-19 10:29:59,617 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
> [0m[0m2017-09-19 10:29:59,729 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) starting
> [0m[0m2017-09-19 10:29:59,822 INFO [org.wildfly.swarm] (MSC service thread 1-1) WFSWARM0019: Install MSC service for command line args: [-Dswarm.logging.periodic-rotating-file-handlers=FILE, -Dswarm.logging.periodic-rotating-file-handlers.FILE.file.path=/var/folders/jm/mpp4zrfn3hx0lmc1jzvx1_s80000gr/T/junit5805521710512368243/junit2910476790071070383.tmp, -Dswarm.logging.root-logger.handlers=[CONSOLE,FILE]]
> [0mCUSTOM LOG FORMAT WARN [org.jboss.as.txn] WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0001: Activating Naming Subsystem
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.io] WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0003: Undertow 1.4.11.Final starting
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0002: Activating Security Subsystem
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0003: Starting Naming Service
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0001: Current PicketBox version=4.9.6.Final
> CUSTOM LOG FORMAT INFO [org.xnio] XNIO version 3.4.3.Final
> CUSTOM LOG FORMAT INFO [org.xnio.nio] XNIO NIO Implementation Version 3.4.3.Final
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0012: Started server default-server.
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0006: Undertow HTTP listener default listening on [0:0:0:0:0:0:0:0]:8080
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0025: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) started in 3573ms - Started 88 of 97 services (18 services are lazy, passive or on-demand)
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm.runtime.deployer] deploying lra-cdi-check.war
> CUSTOM LOG FORMAT INFO [org.jboss.as.server.deployment] WFLYSRV0027: Starting deployment of "lra-cdi-check.war" (runtime-name: "lra-cdi-check.war")
> CUSTOM LOG FORMAT WARN [org.jboss.as.dependency.private] WFLYSRV0018: Deployment "deployment.lra-cdi-check.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> CUSTOM LOG FORMAT INFO [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment lra-cdi-check.war
> CUSTOM LOG FORMAT INFO [org.hibernate.validator.internal.util.Version] HV000001: Hibernate Validator 5.2.4.Final
> CUSTOM LOG FORMAT INFO [org.jboss.weld.Version] WELD-000900: 2.3.5 (Final)
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0018: Host default-host starting
> CUSTOM LOG FORMAT INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.swarm.generated.WildFlySwarmDefaultJAXRSApplication$Proxy$_$$_WeldClientProxy
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0021: Registered web context: /
> CUSTOM LOG FORMAT INFO [org.jboss.as.server] WFLYSRV0010: Deployed "lra-cdi-check.war" (runtime-name : "lra-cdi-check.war")
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0008: Undertow HTTP listener default suspending
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0007: Undertow HTTP listener default stopped, was bound to [0:0:0:0:0:0:0:0]:8080
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0022: Unregistered web context: /
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0019: Host default-host stopping
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0004: Undertow 1.4.11.Final stopping
> CUSTOM LOG FORMAT INFO [org.jboss.as.server.deployment] WFLYSRV0028: Stopped deployment lra-cdi-check.war (runtime-name: lra-cdi-check.war) in 88ms
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0050: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) stopped in 94ms
> CUSTOM LOG FORMAT INFO [org.jboss.weld.Bootstrap] WELD-ENV-002001: Weld SE container internal shut down
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Logging - STABLE org.wildfly.swarm:logging:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Bean Validation - STABLE org.wildfly.swarm:bean-validation:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: CDI Configuration - STABLE org.wildfly.swarm:cdi-config:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Transactions - STABLE org.wildfly.swarm:transactions:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: CDI - STABLE org.wildfly.swarm:cdi:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Undertow - STABLE org.wildfly.swarm:undertow:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: JAX-RS - STABLE org.wildfly.swarm:jaxrs:2017.8.1
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0049: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) starting
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0019: Install MSC service for command line args: [-Dswarm.logging.periodic-rotating-file-handlers=FILE, -Dswarm.logging.periodic-rotating-file-handlers.FILE.file.path=/var/folders/jm/mpp4zrfn3hx0lmc1jzvx1_s80000gr/T/junit411563760007331862/junit474695456187414375.tmp, -Dswarm.logging.root-logger.handlers=[CONSOLE,FILE]]
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0002: Activating Security Subsystem
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0001: Current PicketBox version=4.9.6.Final
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0001: Activating Naming Subsystem
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0003: Starting Naming Service
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.io] WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> CUSTOM LOG FORMAT WARN [org.jboss.as.txn] WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0003: Undertow 1.4.11.Final starting
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0012: Started server default-server.
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0006: Undertow HTTP listener default listening on [0:0:0:0:0:0:0:0]:8080
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0025: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) started in 264ms - Started 88 of 97 services (18 services are lazy, passive or on-demand)
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm.runtime.deployer] deploying lra-cdi-check.war
> CUSTOM LOG FORMAT INFO [org.jboss.as.server.deployment] WFLYSRV0027: Starting deployment of "lra-cdi-check.war" (runtime-name: "lra-cdi-check.war")
> CUSTOM LOG FORMAT WARN [org.jboss.as.dependency.private] WFLYSRV0018: Deployment "deployment.lra-cdi-check.war" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.
> CUSTOM LOG FORMAT INFO [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment lra-cdi-check.war
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0018: Host default-host starting
> CUSTOM LOG FORMAT ERROR [org.jboss.msc.service.fail] MSC000001: Failed to start service jboss.deployment.unit."lra-cdi-check.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."lra-cdi-check.war".WeldStartService: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
> 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)
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.inject.spi.DeploymentException: Method 'compensate' of class 'io.narayana.lra.cdi.bean.AllAnnotationsNoPathBean' annotated by 'io.narayana.lra.annotation.Compensate' should use complementary annotation javax.ws.rs.Path
> at io.narayana.lra.cdi.LraAnnotationProcessingExtension.processLraAnnotatedType(LraAnnotationProcessingExtension.java:128)
> 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:497)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
> at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:313)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:291)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:269)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:197)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:169)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:159)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:224)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:383)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:94)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:204)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:169)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:159)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:224)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:383)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:94)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> ... 3 more
> CUSTOM LOG FORMAT ERROR [org.jboss.as.controller.management-operation] WFLYCTL0013: Operation ("add") failed - address: (("deployment" => "lra-cdi-check.war")) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.inject.spi.DeploymentException: Method 'compensate' of class 'io.narayana.lra.cdi.bean.AllAnnotationsNoPathBean' annotated by 'io.narayana.lra.annotation.Compensate' should use complementary annotation javax.ws.rs.Path
> at io.narayana.lra.cdi.LraAnnotationProcessingExtension.processLraAnnotatedType(LraAnnotationProcessingExtension.java:128)
> 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:497)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
> at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:313)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:291)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:269)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:197)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:169)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:159)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:224)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:383)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:94)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> "},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> CUSTOM LOG FORMAT ERROR [org.jboss.as.server] WFLYSRV0021: Deploy of deployment "lra-cdi-check.war" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService: Failed to start service
> Caused by: org.jboss.weld.exceptions.DefinitionException: Exception List with 1 exceptions:
> Exception 0 :
> javax.enterprise.inject.spi.DeploymentException: Method 'compensate' of class 'io.narayana.lra.cdi.bean.AllAnnotationsNoPathBean' annotated by 'io.narayana.lra.annotation.Compensate' should use complementary annotation javax.ws.rs.Path
> at io.narayana.lra.cdi.LraAnnotationProcessingExtension.processLraAnnotatedType(LraAnnotationProcessingExtension.java:128)
> 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:497)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88)
> at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78)
> at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:313)
> at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:125)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:291)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:269)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:197)
> at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessAnnotatedType(ContainerLifecycleEvents.java:169)
> at org.jboss.weld.bootstrap.BeanDeployer.processAnnotatedTypes(BeanDeployer.java:159)
> at org.jboss.weld.bootstrap.BeanDeployment.createTypes(BeanDeployment.java:224)
> at org.jboss.weld.bootstrap.WeldStartup.startInitialization(WeldStartup.java:383)
> at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:76)
> at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:94)
> 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:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> "},
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"lra-cdi-check.war\".WeldStartService"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
> }
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0019: Host default-host stopping
> CUSTOM LOG FORMAT INFO [org.jboss.as.server.deployment] WFLYSRV0028: Stopped deployment lra-cdi-check.war (runtime-name: lra-cdi-check.war) in 26ms
> CUSTOM LOG FORMAT INFO [org.jboss.as.controller] WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."lra-cdi-check.war".WeldBootstrapService (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."lra-cdi-check.war".CdiValidatorFactoryService, service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator, service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator, WFLYCTL0208: ... and 2 more ]
> service jboss.deployment.unit."lra-cdi-check.war".WeldStartService (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."lra-cdi-check.war".CdiValidatorFactoryService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, WFLYCTL0208: ... and 4 more ]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, service jboss.deployment.unit."lra-cdi-check.war".deploymentCompleteService]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, service jboss.deployment.unit."lra-cdi-check.war".deploymentCompleteService]
> service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, service jboss.deployment.unit."lra-cdi-check.war".deploymentCompleteService]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService, service jboss.deployment.unit."lra-cdi-check.war".deploymentCompleteService]
> service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
> service jboss.deployment.unit."lra-cdi-check.war".ee.ComponentRegistry (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
> service jboss.deployment.unit."lra-cdi-check.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldInitialListener".START, service jboss.deployment.unit."lra-cdi-check.war".component."org.jboss.weld.servlet.WeldTerminalListener".START, service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."lra-cdi-check.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.undertow.deployment.default-server.default-host./ (missing) dependents: [service jboss.deployment.unit."lra-cdi-check.war".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./]
> service jboss.undertow.deployment.default-server.default-host./.codec (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
> service jboss.undertow.deployment.default-server.default-host./.session (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
> service org.wildfly.request-controller.control-point."lra-cdi-check.war".undertow (missing) dependents: [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."lra-cdi-check.war".WeldStartService
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0008: Undertow HTTP listener default suspending
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0007: Undertow HTTP listener default stopped, was bound to [0:0:0:0:0:0:0:0]:8080
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0004: Undertow 1.4.11.Final stopping
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0050: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) stopped in 18ms
> CUSTOM LOG FORMAT INFO [org.jboss.weld.Bootstrap] WELD-ENV-002001: Weld SE container internal shut down
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Logging - STABLE org.wildfly.swarm:logging:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Bean Validation - STABLE org.wildfly.swarm:bean-validation:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: CDI Configuration - STABLE org.wildfly.swarm:cdi-config:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Transactions - STABLE org.wildfly.swarm:transactions:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: CDI - STABLE org.wildfly.swarm:cdi:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: Undertow - STABLE org.wildfly.swarm:undertow:2017.8.1
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0013: Installed fraction: JAX-RS - STABLE org.wildfly.swarm:jaxrs:2017.8.1
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0049: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) starting
> CUSTOM LOG FORMAT INFO [org.wildfly.swarm] WFSWARM0019: Install MSC service for command line args: [-Dswarm.logging.periodic-rotating-file-handlers=FILE, -Dswarm.logging.periodic-rotating-file-handlers.FILE.file.path=/var/folders/jm/mpp4zrfn3hx0lmc1jzvx1_s80000gr/T/junit4960954178688397094/junit1077340550039272742.tmp, -Dswarm.logging.root-logger.handlers=[CONSOLE,FILE]]
> CUSTOM LOG FORMAT WARN [org.jboss.as.txn] WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.io] WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0002: Activating Security Subsystem
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0003: Undertow 1.4.11.Final starting
> CUSTOM LOG FORMAT INFO [org.jboss.as.security] WFLYSEC0001: Current PicketBox version=4.9.6.Final
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0001: Activating Naming Subsystem
> CUSTOM LOG FORMAT INFO [org.jboss.as.naming] WFLYNAM0003: Starting Naming Service
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0012: Started server default-server.
> CUSTOM LOG FORMAT INFO [org.wildfly.extension.undertow] WFLYUT0006: Undertow HTTP listener default listening on [0:0:0:0:0:0:0:0]:8080
> CUSTOM LOG FORMAT INFO [org.jboss.as] WFLYSRV0025: WildFly Swarm 2017.8.1 (WildFly Core 2.2.1.Final) started in 257ms - Started 88 of 97 services (18 services are lazy, passive or on-demand)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2947) LRA client API is still using the old spec
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2947:
--------------------------------------
Summary: LRA client API is still using the old spec
Key: JBTM-2947
URL: https://issues.jboss.org/browse/JBTM-2947
Project: JBoss Transaction Manager
Issue Type: Bug
Components: LRA
Affects Versions: 5.7.0.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.next
The LRA end call in the client API is still expecting the response to contain are array of strings returned by each participant during the termination phase. The spec has since been updated and instead just the current status of the LRA is returned.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2946) LRA quickstart is not spec compliant
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2946?page=com.atlassian.jira.plugin.... ]
Issue was automatically transitioned when Michael Musgrove created pull request #208 in GitHub
----------------------------------------------------------------------------------------------
Status: Pull Request Sent (was: Open)
> LRA quickstart is not spec compliant
> ------------------------------------
>
> Key: JBTM-2946
> URL: https://issues.jboss.org/browse/JBTM-2946
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.7.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
>
> The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
> The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
> In particular look at the code TripCheck.java in commit e2514c4bb3e2b80f0
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2946) LRA quickstart is not spec compliant
by Michael Musgrove (JIRA)
[ https://issues.jboss.org/browse/JBTM-2946?page=com.atlassian.jira.plugin.... ]
Michael Musgrove updated JBTM-2946:
-----------------------------------
Description:
The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
In particular look at the code TripCheck.java in commit e2514c4bb3e2b80f0
was:
The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
> LRA quickstart is not spec compliant
> ------------------------------------
>
> Key: JBTM-2946
> URL: https://issues.jboss.org/browse/JBTM-2946
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Components: LRA
> Affects Versions: 5.7.0.Final
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.next
>
>
> The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
> The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
> In particular look at the code TripCheck.java in commit e2514c4bb3e2b80f0
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2946) LRA quickstart is not spec compliant
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2946:
--------------------------------------
Summary: LRA quickstart is not spec compliant
Key: JBTM-2946
URL: https://issues.jboss.org/browse/JBTM-2946
Project: JBoss Transaction Manager
Issue Type: Bug
Components: LRA
Affects Versions: 5.7.0.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.next
The quickstart interprets the return value from an LRA close call to comprise the business data returned from each participant complete call (as a json array). The spec has since been updated for the LRA close operation to not return business data (since it is considered an anti-pattern in some circles).
The quickstart should revert to an earlier version where the outcome of the "sub bookings" was obtained by querying the services directly (it should still be in the commit history).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBTM-2945) Track SRAs that are started in the context of an LRA
by Michael Musgrove (JIRA)
Michael Musgrove created JBTM-2945:
--------------------------------------
Summary: Track SRAs that are started in the context of an LRA
Key: JBTM-2945
URL: https://issues.jboss.org/browse/JBTM-2945
Project: JBoss Transaction Manager
Issue Type: Enhancement
Components: LRA
Affects Versions: 5.7.0.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Fix For: 5.later
Often an LRA is built up from a number of individual actions performed by the
participants enlisted with the LRA. These participants may use the ACID
guarantees that an SRA provides in order to fulfil the requisite compensatory
and completion actions when the LRA is terminated. To support this requirement
when an SRA is started in the context of an LRA (either by annotating a method
with both the @LRA and @SRA annotations or by starting an SRA via the client
API when an LRA is already active) then the SRA will be automatically
associated with the LRA. The following interface is provided for querying which
LRAs and SRAs are associated with each other (in a one to many relationship):
{code}
public interface LRAToSRA {
/**
* return all the SRAs running in the context of the given LRA
*/
List<SRA> getAssociatedSRAs(URL lraId};
/**
* see if an LRA is associated with the give SRA
*/
URL getAssociatedLRA(URL sraId);
}
{code}
Questions:
- should @Compensate and @Complete block until all associated SRAs have finished
- when an LRA is closed or cancelled should any active SRAs be automatically be committed or rolled back.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months