July 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3225) Decide whether we should make the internal LRA client API not auto closable

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3225?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3225: -------------------------------------- Assignee: (was: Michael Musgrove) > Decide whether we should make the internal LRA client API not auto closable > --------------------------------------------------------------------------- > > Key: JBTM-3225 > URL: https://issues.redhat.com/browse/JBTM-3225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > The LRA implementation contains an internal client API called io.narayana.lra.client.NarayanaLRAClient which implements java.io.Closeable. A recent PR (see issue https://issues.jboss.org/browse/JBTM-3212) made the implementation of the close method a NOOP (since there is no longer any need for cleanup actions). But the method was left empty since there is a possibility that is will be needed in LRA version 1.x where a LRA client API will be added and since there are existing users of the client API. > This task is a reminder to revisit the decision to remove java.io.Closeable prior to releasing an implementation of [version 1.0 of the LRA specification|https://github.com/eclipse/microprofile-lra/issues?q=is%3Ao...]. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3225) Decide whether we should make the internal LRA client API not auto closable

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3225?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3225: ----------------------------------- Priority: Optional (was: Major) > Decide whether we should make the internal LRA client API not auto closable > --------------------------------------------------------------------------- > > Key: JBTM-3225 > URL: https://issues.redhat.com/browse/JBTM-3225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > > The LRA implementation contains an internal client API called io.narayana.lra.client.NarayanaLRAClient which implements java.io.Closeable. A recent PR (see issue https://issues.jboss.org/browse/JBTM-3212) made the implementation of the close method a NOOP (since there is no longer any need for cleanup actions). But the method was left empty since there is a possibility that is will be needed in LRA version 1.x where a LRA client API will be added and since there are existing users of the client API. > This task is a reminder to revisit the decision to remove java.io.Closeable prior to releasing an implementation of [version 1.0 of the LRA specification|https://github.com/eclipse/microprofile-lra/issues?q=is%3Ao...]. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3225) Decide whether we should make the internal LRA client API not auto closable

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3225?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3225: ----------------------------------- Fix Version/s: 5.next > Decide whether we should make the internal LRA client API not auto closable > --------------------------------------------------------------------------- > > Key: JBTM-3225 > URL: https://issues.redhat.com/browse/JBTM-3225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > The LRA implementation contains an internal client API called io.narayana.lra.client.NarayanaLRAClient which implements java.io.Closeable. A recent PR (see issue https://issues.jboss.org/browse/JBTM-3212) made the implementation of the close method a NOOP (since there is no longer any need for cleanup actions). But the method was left empty since there is a possibility that is will be needed in LRA version 1.x where a LRA client API will be added and since there are existing users of the client API. > This task is a reminder to revisit the decision to remove java.io.Closeable prior to releasing an implementation of [version 1.0 of the LRA specification|https://github.com/eclipse/microprofile-lra/issues?q=is%3Ao...]. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3213) Ensure the LRA module is configurable

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3213?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3213: -------------------------------------- Assignee: (was: Michael Musgrove) > Ensure the LRA module is configurable > -------------------------------------- > > Key: JBTM-3213 > URL: https://issues.redhat.com/browse/JBTM-3213 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There are some LRA parameters that we would like to be configurable (timeouts and thread pools for example). Since LRA is a microprofile spec we should leverage microprofile-config for this purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3213) Ensure the LRA module is configurable

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3213?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3213: ----------------------------------- Fix Version/s: 5.next > Ensure the LRA module is configurable > -------------------------------------- > > Key: JBTM-3213 > URL: https://issues.redhat.com/browse/JBTM-3213 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There are some LRA parameters that we would like to be configurable (timeouts and thread pools for example). Since LRA is a microprofile spec we should leverage microprofile-config for this purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3089) LRA code improvements

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3089?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3089: ----------------------------------- Fix Version/s: 5.next > LRA code improvements > --------------------- > > Key: JBTM-3089 > URL: https://issues.redhat.com/browse/JBTM-3089 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Remove TODO comments from the code and replace with JIRA issues. > Ensure that the message string in all occurrences of GenericLRAException are meaningful. > Remove all commented out pieces of code. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3241) Create a test to validate that the LRA coordinator getStatus query returns a state that matches the state model

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3241?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3241: -------------------------------------- Assignee: (was: Michael Musgrove) > Create a test to validate that the LRA coordinator getStatus query returns a state that matches the state model > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3241 > URL: https://issues.redhat.com/browse/JBTM-3241 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA coordinator acts as a participant when LRA's are nested. We need a test that validates that the correct participant states are reported in accordance with Figure 3. Participant State Model of the [LRA participant state model|https://github.com/eclipse/microprofile-lra/blob/master/spec/src/ma...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3241) Create a test to validate that the LRA coordinator getStatus query returns a state that matches the state model

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3241?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3241: ----------------------------------- Fix Version/s: 5.next > Create a test to validate that the LRA coordinator getStatus query returns a state that matches the state model > ---------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3241 > URL: https://issues.redhat.com/browse/JBTM-3241 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA coordinator acts as a participant when LRA's are nested. We need a test that validates that the correct participant states are reported in accordance with Figure 3. Participant State Model of the [LRA participant state model|https://github.com/eclipse/microprofile-lra/blob/master/spec/src/ma...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3108) Renable the maven site plugin for the LRA module

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3108?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3108: ----------------------------------- Fix Version/s: 5.next > Renable the maven site plugin for the LRA module > ------------------------------------------------ > > Key: JBTM-3108 > URL: https://issues.redhat.com/browse/JBTM-3108 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Issue https://issues.jboss.org/browse/JBTM-3093 disabled the site plugin while the MP LRA APIs are still being developed. When MP LRA releases we need to renable the site plugin (used for code coverage tests). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3108) Renable the maven site plugin for the LRA module

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3108?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3108: -------------------------------------- Assignee: (was: Michael Musgrove) > Renable the maven site plugin for the LRA module > ------------------------------------------------ > > Key: JBTM-3108 > URL: https://issues.redhat.com/browse/JBTM-3108 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Issue https://issues.jboss.org/browse/JBTM-3093 disabled the site plugin while the MP LRA APIs are still being developed. When MP LRA releases we need to renable the site plugin (used for code coverage tests). -- 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