January 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3221) Refactor NarayanaLRARecovery according to the specification upgrades

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3221?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3221: ---------------------------------------- [~mmusgrov] please see comment above? > Refactor NarayanaLRARecovery according to the specification upgrades > -------------------------------------------------------------------- > > Key: JBTM-3221 > URL: https://issues.redhat.com/browse/JBTM-3221 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Refactor the NarayanaLRARecovery according to the spec changes in [LRA issue 249|https://github.com/eclipse/microprofile-lra/issues/249]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3229?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3229: ---------------------------------------- [~mmusgrov] Can this be resolved now? > 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, 3 months

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2929?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-2929: ---------------------------------------- [~mmusgrov] this has a fix version of 5.9.7.Final but doesn't seem to be in https://github.com/jbosstm/documentation/compare/5.9.6.Final...5.9.8.Final > 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-2938) LRA participant complete/compensate methods should use HTTP PUT

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2938?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-2938: ---------------------------------------- [~mmusgrov] this has a fix version of 5.9.7.Final but doesn't seem to be in https://github.com/jbosstm/narayana/compare/5.9.6.Final...5.9.8.Final > LRA participant complete/compensate methods should use HTTP PUT > --------------------------------------------------------------- > > Key: JBTM-2938 > URL: https://issues.redhat.com/browse/JBTM-2938 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.7.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.7.Final > > > LRA participant complete and compensate methods are currently called using an HTTP POST request. Since these methods should be idempotent they should respond to PUT since in a REST based system PUT is idempotent and POST is not. > Both the implementation and the specification need changing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2245?page=com.atlassian.jira.plugin... ] Thomas Jenkinson resolved JBTM-2245. ------------------------------------ Resolution: Done > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.redhat.com/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2245?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-2245: ---------------------------------------- [~mmusgrov] this had the fix version of 5.9.7.Final which is wrong we need to track it back > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.redhat.com/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2245?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-2245: ----------------------------------- Fix Version/s: (was: 5.9.7.Final) > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.redhat.com/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2245) Narayana TM should act upon wildfly suspend calls

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-2245?page=com.atlassian.jira.plugin... ] Thomas Jenkinson reopened JBTM-2245: ------------------------------------ > Narayana TM should act upon wildfly suspend calls > ------------------------------------------------- > > Key: JBTM-2245 > URL: https://issues.redhat.com/browse/JBTM-2245 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration, XTS > Affects Versions: 5.0.2 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > > Wildfly now supports suspend [notifications | http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002862.html] > The design discussion is [here| http://lists.jboss.org/pipermail/wildfly-dev/2014-June/002296.html] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3062) Include a test for LRA context propagation across a "non-LRA aware" service

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3062?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3062: ---------------------------------------- And the resolution set to something to indicate duplicate rather than done > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.redhat.com/browse/JBTM-3062 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.7.Final > > > If a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and service A in turn calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. A test is needed for this behaviour. > This issue relates to https://github.com/eclipse/microprofile-lra/issues/7 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3062) Include a test for LRA context propagation across a "non-LRA aware" service

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3062?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3062: ---------------------------------------- [~mmusgrov] I think the fix version should be removed > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.redhat.com/browse/JBTM-3062 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.9.7.Final > > > If a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and service A in turn calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. A test is needed for this behaviour. > This issue relates to https://github.com/eclipse/microprofile-lra/issues/7 -- 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 January 2020