March 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3086) dependentLRA test failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3086: ---------------------------------------- Moved to 5.later since the LRA Java API will not be available in the initial release. > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.later > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/...] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/sr...] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3086) dependentLRA test failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3086: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.later > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/...] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/sr...] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3116) Temporarily disable LRA quickstarts until the MP LRA spec is more stable

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3116?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #246 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Temporarily disable LRA quickstarts until the MP LRA spec is more stable > ------------------------------------------------------------------------ > > Key: JBTM-3116 > URL: https://issues.jboss.org/browse/JBTM-3116 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator, LRA > Affects Versions: 5.9.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The MP LRA draft spec has recently undergone a lot of churn and we need to bring both the narayana implementation and the quickstarts into line with those changes. While that work is being undertaken the quickstarts should be disabled so that users and CI do not use non-working examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3116) Temporarily disable LRA quickstarts until the MP LRA spec is more stable

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3116: -------------------------------------- Summary: Temporarily disable LRA quickstarts until the MP LRA spec is more stable Key: JBTM-3116 URL: https://issues.jboss.org/browse/JBTM-3116 Project: JBoss Transaction Manager Issue Type: Task Components: Demonstrator, LRA Affects Versions: 5.9.3.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The MP LRA draft spec has recently undergone a lot of churn and we need to bring both the narayana implementation and the quickstarts into line with those changes. While that work is being undertaken the quickstarts should be disabled so that users and CI do not use non-working examples. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3114) LRA module should depend on a specific snapshot build

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3114?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3114: ---------------------------------------- Note that this issue should also apply to the quickstart and conference repos. My recommendation is to disable those until the API is stabilised. > LRA module should depend on a specific snapshot build > ----------------------------------------------------- > > Key: JBTM-3114 > URL: https://issues.jboss.org/browse/JBTM-3114 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > The Narayana implementation of the LRA spec should depend on specific LRA API snapshot builds (since the LRA API is a moving target). > This problem has been fixed in JBTM-3091 and reintroduced in https://github.com/jbosstm/narayana/pull/1408/files#diff-14510da88f467b20.... > Current version of the implementation is running against latest build: > - api - 1.0-20190222.071200-278 > - tck - 1.0-20190222.071201-278 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3042: ---------------------------------------- Moved fix version to 5.later since the LRA java API will not be available in the initial release > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > 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.later > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/ma... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3042: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > 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.later > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/ma... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3065) Check that starting LRA's via CDI and API in the same method works

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3065?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3065: ---------------------------------------- Moved fix version to 5.later since the LRA java API will not be available in the initial release > Check that starting LRA's via CDI and API in the same method works > ------------------------------------------------------------------ > > Key: JBTM-3065 > URL: https://issues.jboss.org/browse/JBTM-3065 > 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.later > > > The LRA spec supports starting LRA's via a Java API or via Java annotations. If the two approaches are used together in the same resource method then the LRA started via the API should be nested inside the one started by an annotation. > If the annotated class also contains @Compensate and @Complete annotations (which means that the resource should join the outer LRA) and the resource method Joins the nested LRA then the resource should receive callbacks for both the outer and nested LRA's. > The following code shows an example: > {code} > @PUT > @LRA(LRA.Type.REQUIRES_NEW) // starts a new LRA on entry > public String doInTransaction() { > URL lraId = lraClient.startLRA(...); // starts a nested LRA > lraClient.join(...) // join the nested LRA > lraClient.closeLRA(lraId); // close the nested LRA > // assert that the nested callbacks were invoked > // assert that the callbacks for the outer LRA have not been called yet > } > {code} > Similar comments apply if the resource joins via the LRAManagement API: > {code} > @Inject > private LRAManagement lraManagement; > public String doInTransaction() { > lraManagement.joinLRA(this, lraId, 0L, TimeUnit.SECONDS); > // etc > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3065) Check that starting LRA's via CDI and API in the same method works

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3065?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3065: ----------------------------------- Fix Version/s: 5.later (was: 5.next) > Check that starting LRA's via CDI and API in the same method works > ------------------------------------------------------------------ > > Key: JBTM-3065 > URL: https://issues.jboss.org/browse/JBTM-3065 > 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.later > > > The LRA spec supports starting LRA's via a Java API or via Java annotations. If the two approaches are used together in the same resource method then the LRA started via the API should be nested inside the one started by an annotation. > If the annotated class also contains @Compensate and @Complete annotations (which means that the resource should join the outer LRA) and the resource method Joins the nested LRA then the resource should receive callbacks for both the outer and nested LRA's. > The following code shows an example: > {code} > @PUT > @LRA(LRA.Type.REQUIRES_NEW) // starts a new LRA on entry > public String doInTransaction() { > URL lraId = lraClient.startLRA(...); // starts a nested LRA > lraClient.join(...) // join the nested LRA > lraClient.closeLRA(lraId); // close the nested LRA > // assert that the nested callbacks were invoked > // assert that the callbacks for the outer LRA have not been called yet > } > {code} > Similar comments apply if the resource joins via the LRAManagement API: > {code} > @Inject > private LRAManagement lraManagement; > public String doInTransaction() { > lraManagement.joinLRA(this, lraId, 0L, TimeUnit.SECONDS); > // etc > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3104) Define a separate CI profile for LRA

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3104?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-3104 at 3/4/19 10:38 AM: ----------------------------------------------------------------- [~ochaloup] I am reassigning to you since you understand how the set of profiles in the lra-test module interact with each other. Note also that I had to disable running the TCK by default (see JBTM-3115). But do let me know if you disagree and I will take another look. was (Author: mmusgrov): [~ochaloup] I am reassigning to you since you understand how the set of profiles in the lra-test module interact with each other. Note also that I had to disable running the TCK by default (see JBTM-3115). > Define a separate CI profile for LRA > ------------------------------------ > > Key: JBTM-3104 > URL: https://issues.jboss.org/browse/JBTM-3104 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System, LRA > Reporter: Tom Jenkinson > Assignee: Ondra Chaloupka > Priority: Major > > This could be similar to how the XTS and RTS profile is constructed. > Changes are anticipated in the narayana.sh, maybe pom IDK, and the pull job and main job -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues March 2019