August 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3352) Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3352?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3352: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API > ---------------------------------------------------------------------------------------- > > Key: JBTM-3352 > URL: https://issues.redhat.com/browse/JBTM-3352 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The LRA Coordinator API contains the no more used and misguiding flag "effectivelyActive" for the `/status` API method. This should be removed to clean the API. > At the same time the API contains API method of "isActive" returning the Active status for LRA. This duplicates the functionality of the `status` endpoint and it's not needed. The API should be cleand from it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3353) Narayana starter compatibility information for Spring Boot 2.3.2

by Chris Laprun (Jira)

[ https://issues.redhat.com/browse/JBTM-3353?page=com.atlassian.jira.plugin... ] Chris Laprun closed JBTM-3353. ------------------------------ Resolution: Duplicate Issue > Narayana starter compatibility information for Spring Boot 2.3.2 > ---------------------------------------------------------------- > > Key: JBTM-3353 > URL: https://issues.redhat.com/browse/JBTM-3353 > Project: JBoss Transaction Manager > Issue Type: Task > Reporter: Chris Laprun > Priority: Major > > The Snowdrop team is really pleased to inform you that we're planning to release a new Snowdrop BOM on *14 Sep 2020* > based on Spring Boot *2.3.2*. > Some of our artifacts depend on your product and would, therefore, need to know which product version we should be > using for this new release which we intend to support until *30 Sep 2021*. > We expect to start testing our new release based on Spring Boot *2.3.2* on *18 Aug 2020*. > We would therefore request a support statement from your team in the form of the following information: > - Product name and version (e.g. JWS - 5.3.1) > - Supported version (e.g. 9.0.30-redhat-00001) > - Date of end of support > - PNC/Indy URL (e.g. [http://indy.psi.redhat.com/browse/maven/]...) > - MRRC URL, if already released (e.g. [https://maven.repository.redhat.com/ga/]...) > Please let us know if the product support will lapse before *30 Sep 2021*. > Thank you in advance for your help! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3354) Narayana starter compatibility information for Spring Boot 2.3.2

by Chris Laprun (Jira)

Chris Laprun created JBTM-3354: ---------------------------------- Summary: Narayana starter compatibility information for Spring Boot 2.3.2 Key: JBTM-3354 URL: https://issues.redhat.com/browse/JBTM-3354 Project: JBoss Transaction Manager Issue Type: Task Reporter: Chris Laprun The Snowdrop team is really pleased to inform you that we're planning to release a new Snowdrop BOM on *14 Sep 2020* based on Spring Boot *2.3.2*. Some of our artifacts depend on your product and would, therefore, need to know which product version we should be using for this new release which we intend to support until *30 Sep 2021*. We expect to start testing our new release based on Spring Boot *2.3.2* on *21 Aug 2020*. We would therefore request a support statement from your team in the form of the following information: - Product name and version (e.g. JWS - 5.3.1) - Supported version (e.g. 9.0.30-redhat-00001) - Date of end of support - PNC/Indy URL (e.g. [http://indy.psi.redhat.com/browse/maven/]...) - MRRC URL, if already released (e.g. [https://maven.repository.redhat.com/ga/]...) Please let us know if the product support will lapse before *30 Sep 2021*. Thank you in advance for your help! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3353) Narayana starter compatibility information for Spring Boot 2.3.2

by Chris Laprun (Jira)

Chris Laprun created JBTM-3353: ---------------------------------- Summary: Narayana starter compatibility information for Spring Boot 2.3.2 Key: JBTM-3353 URL: https://issues.redhat.com/browse/JBTM-3353 Project: JBoss Transaction Manager Issue Type: Task Reporter: Chris Laprun The Snowdrop team is really pleased to inform you that we're planning to release a new Snowdrop BOM on *14 Sep 2020* based on Spring Boot *2.3.2*. Some of our artifacts depend on your product and would, therefore, need to know which product version we should be using for this new release which we intend to support until *30 Sep 2021*. We expect to start testing our new release based on Spring Boot *2.3.2* on *18 Aug 2020*. We would therefore request a support statement from your team in the form of the following information: - Product name and version (e.g. JWS - 5.3.1) - Supported version (e.g. 9.0.30-redhat-00001) - Date of end of support - PNC/Indy URL (e.g. [http://indy.psi.redhat.com/browse/maven/]...) - MRRC URL, if already released (e.g. [https://maven.repository.redhat.com/ga/]...) Please let us know if the product support will lapse before *30 Sep 2021*. Thank you in advance for your help! -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3352) Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3352?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3352: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1655 > Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API > ---------------------------------------------------------------------------------------- > > Key: JBTM-3352 > URL: https://issues.redhat.com/browse/JBTM-3352 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The LRA Coordinator API contains the no more used and misguiding flag "effectivelyActive" for the `/status` API method. This should be removed to clean the API. > At the same time the API contains API method of "isActive" returning the Active status for LRA. This duplicates the functionality of the `status` endpoint and it's not needed. The API should be cleand from it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3352) Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3352: -------------------------------------- Summary: Remove "effectivellyActive" and deprecated status endpoints from the LRA Coordinator API Key: JBTM-3352 URL: https://issues.redhat.com/browse/JBTM-3352 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.10.5.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The LRA Coordinator API contains the no more used and misguiding flag "effectivelyActive" for the `/status` API method. This should be removed to clean the API. At the same time the API contains API method of "isActive" returning the Active status for LRA. This duplicates the functionality of the `status` endpoint and it's not needed. The API should be cleand from it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2929) Create LRA documentation

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2929?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-2929: ----------------------------------- Priority: Blocker (was: Major) > Create LRA documentation > ------------------------ > > Key: JBTM-2929 > URL: https://issues.redhat.com/browse/JBTM-2929 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation, LRA > Affects Versions: 5.6.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.9.7.Final > > > Add LRA documentation. > The documentation is intended to be a MicroProfile specification and is available in the sandbox: https://github.com/eclipse/microprofile-sandbox/pull/2/files#diff-eeb2668... (which is part of PR https://github.com/eclipse/microprofile-sandbox/pull/2) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2929) Create LRA documentation

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-2929?page=com.atlassian.jira.plugin... ] Michael Musgrove reopened JBTM-2929: ------------------------------------ I have reopened this issue since we also need some documentation in our own docs that explain our particular implementation of MP LRA specification. > Create LRA documentation > ------------------------ > > Key: JBTM-2929 > URL: https://issues.redhat.com/browse/JBTM-2929 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Documentation, LRA > Affects Versions: 5.6.4.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.7.Final > > > Add LRA documentation. > The documentation is intended to be a MicroProfile specification and is available in the sandbox: https://github.com/eclipse/microprofile-sandbox/pull/2/files#diff-eeb2668... (which is part of PR https://github.com/eclipse/microprofile-sandbox/pull/2) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3289) Allow LRA method execution when for closed LRA when the LRA is nested and the participant is already registered

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3289?page=com.atlassian.jira.plugin... ] Martin Stefanko resolved JBTM-3289. ----------------------------------- Resolution: Done The unignored test - {{TckTests#mixedMultiLevelNestedActivity}} is passing with the current master branch so this must have been fixed in a different PR. > Allow LRA method execution when for closed LRA when the LRA is nested and the participant is already registered > --------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3289 > URL: https://issues.redhat.com/browse/JBTM-3289 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > See https://github.com/eclipse/microprofile-lra/issues/274 and https://github.com/eclipse/microprofile-lra/pull/276. > Depends on https://github.com/eclipse/microprofile-lra/pull/293. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3351) clearHeuristic management operation should clear participant's heuristic flag as well as it clears the transaction heuristic flag

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3351?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3351: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1653 > clearHeuristic management operation should clear participant's heuristic flag as well as it clears the transaction heuristic flag > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-3351 > URL: https://issues.redhat.com/browse/JBTM-3351 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration, Transaction Core > Affects Versions: 5.10.5.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The management operation {{clearHeuristic}} should consider to clear heuristic flag not only from the transaction ({{BasicAction}}) but from the participant record as well - when possible, e.g. the XA resource record maintains heuristic flag for participant and thus it should be cleared on the operation. > The current management operation {{'clearHeuristic'}} is invoked only on the "covering" transaction - {{BasicAction}} is modified[1] -> [2] -> [3]. But the {{XAResourceRecord}} heuristics state[4] is unchanged. Then during recovery commit retry the {{XAResource.commit}} is denied[5]. > [1] https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaCore/arjuna/c... > [2] https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaCore/arjuna/c... > [3] https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaCore/arjuna/c... > [4] https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaJTA/jta/class... > [5] https://github.com/jbosstm/narayana/blob/5.10.5.Final/ArjunaJTA/jta/class... -- This message was sent by Atlassian Jira (v7.13.8#713008)

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