July 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3208) Include an LRA quickstart that includes an embedded coordinator

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3208?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3208: ----------------------------------- Fix Version/s: 5.next (was: 5.9.8.Final) > Include an LRA quickstart that includes an embedded coordinator > --------------------------------------------------------------- > > Key: JBTM-3208 > URL: https://issues.redhat.com/browse/JBTM-3208 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA quickstarts all use an external coordinator for managing the lifecycle of an LRA. We should include a quickstart the demonstrates how to embed the coordinator with the service. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3208) Include an LRA quickstart that includes an embedded coordinator

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3208?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3208: -------------------------------------- Assignee: (was: Michael Musgrove) > Include an LRA quickstart that includes an embedded coordinator > --------------------------------------------------------------- > > Key: JBTM-3208 > URL: https://issues.redhat.com/browse/JBTM-3208 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA quickstarts all use an external coordinator for managing the lifecycle of an LRA. We should include a quickstart the demonstrates how to embed the coordinator with the service. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3250) LRA caches ids of LRAs but this cache can become stale in cloud native environments

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3250?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3250: ----------------------------------- Fix Version/s: 5.next > LRA caches ids of LRAs but this cache can become stale in cloud native environments > ----------------------------------------------------------------------------------- > > Key: JBTM-3250 > URL: https://issues.redhat.com/browse/JBTM-3250 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA implementation [caches active and recovering LRAs|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordina...]. But this cache can become stale is cloud native environments. Since an LRA is always stored in our logs from the moment of creation until successful completion a better option would be to always read the current list from the logs. This approach will facilitate use of the implementation in environments where coordinators come and go. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3250) LRA caches ids of LRAs but this cache can become stale in cloud native environments

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3250?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3250: -------------------------------------- Assignee: Michael Musgrove > LRA caches ids of LRAs but this cache can become stale in cloud native environments > ----------------------------------------------------------------------------------- > > Key: JBTM-3250 > URL: https://issues.redhat.com/browse/JBTM-3250 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > The LRA implementation [caches active and recovering LRAs|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordina...]. But this cache can become stale is cloud native environments. Since an LRA is always stored in our logs from the moment of creation until successful completion a better option would be to always read the current list from the logs. This approach will facilitate use of the implementation in environments where coordinators come and go. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3220) TckContextTests.testForget failed

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3220?page=com.atlassian.jira.plugin... ] Michael Musgrove closed JBTM-3220. ---------------------------------- Resolution: Out of Date This issue is now fixed (there have been a number of changes relating to when the forget method is invoked and I suspect one of them resolved this issue). > TckContextTests.testForget failed > --------------------------------- > > Key: JBTM-3220 > URL: https://issues.redhat.com/browse/JBTM-3220 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.0.Final > > > TckContextTests.testForget:154 testForget resource status should have been called expected:<1> but was:<2> seems to fail consistently on the narayana LRA branch but it works fine on the Narayana master. I would recommend that we use this JIRA to capture any further CI LRA tck test failures. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3299) Expose optional additional description of LRARecord status

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3299?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3299: ----------------------------------- Fix Version/s: 5.next > Expose optional additional description of LRARecord status > ---------------------------------------------------------- > > Key: JBTM-3299 > URL: https://issues.redhat.com/browse/JBTM-3299 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > The LRA record can be in a state, for instance, Completing or Compensating into which it got based on different criteria: > * on users request (by user returning 202 status code from Complete or Compensate method) > * because the Complete or Compensate invocation didn't succeed and the coordinator will retry in the next recovery run > This distinction may be useful for users querying LRAs so we can include it in the JSON response representing the LRARecord. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3205) LRA Spring Boot + JAX-RS support

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3205?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3205: ---------------------------------------- This issue has been verified as fixed by the reporter so I am closing it as resolved. > LRA Spring Boot + JAX-RS support > -------------------------------- > > Key: JBTM-3205 > URL: https://issues.redhat.com/browse/JBTM-3205 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Major > > I created this enhancement for tracking all issues for Spring Boot + JAX-RS application. > {code:xml} > ... > <parent> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-parent</artifactId> > <version>2.1.6.RELEASE</version> > <relativePath/>  > </parent> > ... > <dependencies> >  > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-jersey</artifactId> > </dependency> > ... > </dependencies> > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3071) Windows automation of the LRA examples quickstarts

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3071?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3071: -------------------------------------- Assignee: (was: Michael Musgrove) > Windows automation of the LRA examples quickstarts > -------------------------------------------------- > > Key: JBTM-3071 > URL: https://issues.redhat.com/browse/JBTM-3071 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA examples quickstarts (https://issues.jboss.org/browse/JBTM-3063) contain a bash script to run the examples. We need the equivalent for running on Windows. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3298) Check that LRA participants are called in reverse order if there are no retries

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3298?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3298: ----------------------------------- Fix Version/s: 5.next > Check that LRA participants are called in reverse order if there are no retries > ------------------------------------------------------------------------------- > > Key: JBTM-3298 > URL: https://issues.redhat.com/browse/JBTM-3298 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA spec says that under non failure conditions LRA participants SHOULD be called in reverse order of there enlistment. Note that if retries are required then those participants will be processed out of order (which is fine since the spec does not preclude this). > This JIRA is asking for a test for this behaviour and to provide a fix if they aren't called in reverse order. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3071) Windows automation of the LRA examples quickstarts

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3071?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3071: ----------------------------------- Fix Version/s: 5.next > Windows automation of the LRA examples quickstarts > -------------------------------------------------- > > Key: JBTM-3071 > URL: https://issues.redhat.com/browse/JBTM-3071 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA examples quickstarts (https://issues.jboss.org/browse/JBTM-3063) contain a bash script to run the examples. We need the equivalent for running on Windows. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 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 July 2020