May 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3022) The build should build the (deprecated) lra-annotations module

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3022?page=com.atlassian.jira.plugin.... ] Amos Feng closed JBTM-3022. --------------------------- > The build should build the (deprecated) lra-annotations module > -------------------------------------------------------------- > > Key: JBTM-3022 > URL: https://issues.jboss.org/browse/JBTM-3022 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.8.2.Final > > > the lra parent pom should include a build of the lra-annotations module: > <module>lra-annotations</module> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3024) Make sure top level README says how to build the eclipse microprofile-lra artifacts

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-3024?page=com.atlassian.jira.plugin.... ] Amos Feng closed JBTM-3024. --------------------------- > Make sure top level README says how to build the eclipse microprofile-lra artifacts > ----------------------------------------------------------------------------------- > > Key: JBTM-3024 > URL: https://issues.jboss.org/browse/JBTM-3024 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.8.2.Final > > > The lra subsystem depends on the microprofile-lra artifacts which are in a separate repo. build.sh and build.bat need build these dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3024) Make sure top level README says how to build the eclipse microprofile-lra artifacts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3024?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3024: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Make sure top level README says how to build the eclipse microprofile-lra artifacts > ----------------------------------------------------------------------------------- > > Key: JBTM-3024 > URL: https://issues.jboss.org/browse/JBTM-3024 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The lra subsystem depends on the microprofile-lra artifacts which are in a separate repo. build.sh and build.bat need build these dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3023) Add a test to show compensations being retried after a network error

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3023?page=com.atlassian.jira.plugin.... ] Michael Musgrove closed JBTM-3023. ---------------------------------- Resolution: Rejected Will fix as part of https://issues.jboss.org/browse/JBTM-2978 instead > Add a test to show compensations being retried after a network error > -------------------------------------------------------------------- > > Key: JBTM-3023 > URL: https://issues.jboss.org/browse/JBTM-3023 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.later > > > The fix for JBTM-2978 (Compensation should not be considered done in case of network error) needs an automated test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2958) Wrong format of the Link header on joining LRA by participant should return error to the participant

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2958?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2958: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Wrong format of the Link header on joining LRA by participant should return error to the participant > ---------------------------------------------------------------------------------------------------- > > Key: JBTM-2958 > URL: https://issues.jboss.org/browse/JBTM-2958 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Ondra Chaloupka > Assignee: Michael Musgrove > > If there is a participant joining a started LRA which uses wrong format of {{Link}} header then {{NullPointer}} is logged to the swarm server log. But client gets status {{OK}}. > Client should be informed that enlistment failed and there should not be nullpointer in the log. > NullPointer > {code} > INFO [io.narayana.lra] (default task-4) Cannot extract compensator from link'http://localhost': java.lang.IllegalArgumentException: RESTEASY003960: Unable to parse Link header. No end to parameter: http://localhost > at org.jboss.resteasy.plugins.delegates.LinkDelegate$Parser.parseAttribute(LinkDelegate.java:112) > at org.jboss.resteasy.plugins.delegates.LinkDelegate$Parser.parse(LinkDelegate.java:63) > at org.jboss.resteasy.plugins.delegates.LinkDelegate.fromString(LinkDelegate.java:160) > at org.jboss.resteasy.plugins.delegates.LinkDelegate.fromString(LinkDelegate.java:23) > at org.jboss.resteasy.specimpl.LinkImpl.valueOf(LinkImpl.java:31) > at org.jboss.resteasy.specimpl.LinkBuilderImpl.link(LinkBuilderImpl.java:34) > at javax.ws.rs.core.Link.valueOf(Link.java:173) > at io.narayana.lra.coordinator.domain.model.LRARecord.extractCompensator(LRARecord.java:150) > at io.narayana.lra.coordinator.domain.model.Transaction.findLRAParticipant(Transaction.java:498) > at io.narayana.lra.coordinator.domain.model.Transaction.enlistParticipant(Transaction.java:428) > at io.narayana.lra.coordinator.domain.service.LRAService.joinLRA(LRAService.java:268) > at io.narayana.lra.coordinator.domain.service.LRAService$Proxy$_$$_WeldClientProxy.joinLRA(Unknown Source) > at io.narayana.lra.coordinator.api.Coordinator.joinLRA(Coordinator.java:468) > at io.narayana.lra.coordinator.api.Coordinator.joinLRAViaBody(Coordinator.java:406) > at io.narayana.lra.coordinator.api.Coordinator$Proxy$_$$_WeldClientProxy.joinLRAViaBody(Unknown Source) > 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:498) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:402) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209) > at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.swarm.generated.FaviconErrorHandler.handleRequest(FaviconErrorHandler.java:62) > at io.undertow.server.handlers.PathHandler.handleRequest(PathHandler.java:94) > at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292) > at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138) > at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272) > at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:211) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {code} > The ok return code: > {code} > curl -i -X PUT -H "Link: http://localhost" http://localhost:8080/lra-coordinator/0_ffff0a000007_-39bdc3dc_5a098390_d > HTTP/1.1 200 OK > Connection: keep-alive > Long-Running-Action-Recovery: http://localhost:8080/lra-recovery-coordinator/http%3A%2F%2Flocalhost%3A8... > Location: http://localhost:8080/lra-recovery-coordinator/http%3A%2F%2Flocalhost%3A8... > Content-Type: application/json > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3024) Make sure top level README says how to build the eclipse microprofile-lra artifacts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3024?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1320 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Make sure top level README says how to build the eclipse microprofile-lra artifacts > ----------------------------------------------------------------------------------- > > Key: JBTM-3024 > URL: https://issues.jboss.org/browse/JBTM-3024 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The lra subsystem depends on the microprofile-lra artifacts which are in a separate repo. build.sh and build.bat need build these dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3024) Make sure top level README says how to build the eclipse microprofile-lra artifacts

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3024?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3024: ----------------------------------- Summary: Make sure top level README says how to build the eclipse microprofile-lra artifacts (was: Make sure build.sh builds the microprofile-lra artifacts) > Make sure top level README says how to build the eclipse microprofile-lra artifacts > ----------------------------------------------------------------------------------- > > Key: JBTM-3024 > URL: https://issues.jboss.org/browse/JBTM-3024 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.8.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The lra subsystem depends on the microprofile-lra artifacts which are in a separate repo. build.sh and build.bat need build these dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3024) Make sure build.sh builds the microprofile-lra artifacts

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3024: -------------------------------------- Summary: Make sure build.sh builds the microprofile-lra artifacts Key: JBTM-3024 URL: https://issues.jboss.org/browse/JBTM-3024 Project: JBoss Transaction Manager Issue Type: Task Components: Build System Affects Versions: 5.8.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The lra subsystem depends on the microprofile-lra artifacts which are in a separate repo. build.sh and build.bat need build these dependencies. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3023) Add a test to show compensations being retried after a network error

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3023: -------------------------------------- Summary: Add a test to show compensations being retried after a network error Key: JBTM-3023 URL: https://issues.jboss.org/browse/JBTM-3023 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.8.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.later The fix for JBTM-2978 (Compensation should not be considered done in case of network error) needs an automated test. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2982) LRA participant completion calls during recovery do not timeout

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2982?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2982: ---------------------------------------- This recovery part of this issue is fixed by JBTM-2977. > LRA participant completion calls during recovery do not timeout > --------------------------------------------------------------- > > Key: JBTM-2982 > URL: https://issues.jboss.org/browse/JBTM-2982 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > > Participants that do not respond to completion/compensation requests in timely fashion can delay the caller indefinitely. This applies to periodic recovery attempts to contact participants (and to participant calls as a result of LRA close/cancel requests). > The issue also blocks the ability to shutdown the server. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues May 2018