December 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3229) Allow to enlist AfterLRA listeners after the LRA enters the ending phase

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3229?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3229: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1536 > Allow to enlist AfterLRA listeners after the LRA enters the ending phase > ------------------------------------------------------------------------ > > Key: JBTM-3229 > URL: https://issues.redhat.com/browse/JBTM-3229 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > https://github.com/eclipse/microprofile-lra/issues/241 > The specification was updated to allow AfterLRA listeners (LRA resources without Compensate method but with the AfterLRA method) to enlist for AfterLRA notification even after the LRA enters the ending (closing/canceling) phase. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3229) Allow to enlist AfterLRA listeners after the LRA enters the ending phase

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3229: ------------------------------------- Summary: Allow to enlist AfterLRA listeners after the LRA enters the ending phase Key: JBTM-3229 URL: https://issues.redhat.com/browse/JBTM-3229 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.1.Final Reporter: Martin Stefanko Assignee: Martin Stefanko https://github.com/eclipse/microprofile-lra/issues/241 The specification was updated to allow AfterLRA listeners (LRA resources without Compensate method but with the AfterLRA method) to enlist for AfterLRA notification even after the LRA enters the ending (closing/canceling) phase. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3228) Nested LRA participants should have Forget methods called when the parent LRA is closed

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3228?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3228: ---------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/jbosstm/narayana/pull/1535 > Nested LRA participants should have Forget methods called when the parent LRA is closed > --------------------------------------------------------------------------------------- > > Key: JBTM-3228 > URL: https://issues.redhat.com/browse/JBTM-3228 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > https://github.com/eclipse/microprofile-lra/issues/208 > According to the specification, we should call Forget on nested LRA participants when the parent LRA is closed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3228) Nested LRA participants should have Forget methods called when the parent LRA is closed

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3228?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3228: ---------------------------------- Summary: Nested LRA participants should have Forget methods called when the parent LRA is closed (was: Nested LRA participant should have Forget methods called when the parent LRA is closed) > Nested LRA participants should have Forget methods called when the parent LRA is closed > --------------------------------------------------------------------------------------- > > Key: JBTM-3228 > URL: https://issues.redhat.com/browse/JBTM-3228 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > https://github.com/eclipse/microprofile-lra/issues/208 > According to the specification, we should call Forget on nested LRA participants when the parent LRA is closed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3228) Nested LRA participant should have Forget methods called when the parent LRA is closed

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3228: ------------------------------------- Summary: Nested LRA participant should have Forget methods called when the parent LRA is closed Key: JBTM-3228 URL: https://issues.redhat.com/browse/JBTM-3228 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.1.Final Reporter: Martin Stefanko Assignee: Martin Stefanko https://github.com/eclipse/microprofile-lra/issues/208 According to the specification, we should call Forget on nested LRA participants when the parent LRA is closed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3228) Nested LRA participant should have Forget methods called when the parent LRA is closed

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3228?page=com.atlassian.jira.plugin... ] Work on JBTM-3228 started by Martin Stefanko. --------------------------------------------- > Nested LRA participant should have Forget methods called when the parent LRA is closed > -------------------------------------------------------------------------------------- > > Key: JBTM-3228 > URL: https://issues.redhat.com/browse/JBTM-3228 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > https://github.com/eclipse/microprofile-lra/issues/208 > According to the specification, we should call Forget on nested LRA participants when the parent LRA is closed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3227) LRA branch TckTests#TestForget is failing on our CI infrastructure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3227?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1534 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > LRA branch TckTests#TestForget is failing on our CI infrastructure > ------------------------------------------------------------------ > > Key: JBTM-3227 > URL: https://issues.jboss.org/browse/JBTM-3227 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > The LRA branch tracks MP-LRA changes and we test it on our CI set up. > The branch depends on snapshot builds but the current build is failing because the test TckTests#TestForget is wrong and it has been fixed in a later snapshot. Therefore we need to upgrade the snapshot build dependency -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3227) LRA branch TckTests#TestForget is failing on our CI infrastructure

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3227: -------------------------------------- Summary: LRA branch TckTests#TestForget is failing on our CI infrastructure Key: JBTM-3227 URL: https://issues.jboss.org/browse/JBTM-3227 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA, Testing Reporter: Michael Musgrove Assignee: Michael Musgrove The LRA branch tracks MP-LRA changes and we test it on our CI set up. The branch depends on snapshot builds but the current build is failing because the test TckTests#TestForget is wrong and it has been fixed in a later snapshot. Therefore we need to upgrade the snapshot build dependency -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Thomas Jenkinson updated JBTM-741: ---------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Priority: Minor > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2116) SPI: Unique identifier for a transaction

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2116?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2116: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > SPI: Unique identifier for a transaction > ---------------------------------------- > > Key: JBTM-2116 > URL: https://issues.jboss.org/browse/JBTM-2116 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: SPI > Reporter: Jesper Pedersen > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The Narayana SPI should provide a method that returns a unique identifier for a transaction that is stable for its entire lifecycle. > {noformat} > public Object getIdentifier(Transaction tx) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 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 December 2019