March 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3071) Windows automation of the LRA examples quickstarts

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3071?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3071: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > Windows automation of the LRA examples quickstarts > -------------------------------------------------- > > Key: JBTM-3071 > URL: https://issues.jboss.org/browse/JBTM-3071 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA examples quickstarts (https://issues.jboss.org/browse/JBTM-3063) contain a bash script to run the examples. We need the equivalent for running on Windows. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

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.jboss.org/browse/JBTM-3062?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3062: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > Include a test for LRA context propagation across a "non-LRA aware" service > --------------------------------------------------------------------------- > > Key: JBTM-3062 > URL: https://issues.jboss.org/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.next > > > 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.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3072: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose > ---------------------------------------------------------------------------------------- > > Key: JBTM-3072 > URL: https://issues.jboss.org/browse/JBTM-3072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a test that verifies the correct behaviour when a method is annotated with both REQUIRES_NEW and delayClose, ie something like: > {code} > @PUT > @Path(ActivityController.ACCEPT_WORK) > @LRA(value = LRA.Type.REQUIRES_NEW, delayClose = true) > public Response doInNewLRA( ....) {...} > {code} > The expected behaviour is: > {code} > /** > * If called outside a LRA context a new LRA will be created for the > * the duration of the method call and when the call completes it will > * be closed (this behaviour can be overridden using the > * {@link LRA#delayClose} attribute). > * > * If called inside a LRA context it will be suspended and a new LRA > * context will be created for the duration of the call. When the method > * finishes this new LRA will be closed and the original context will be > * resumed. This behaviour can be overridden using the > * {@link LRA#delayClose} attribute) in which case the original LRA > * remains suspended and the new LRA becomes the active one and only > * when that one is terminated will the original context be resumed. > */ > REQUIRES_NEW, > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3073) Do not mandate JAX-RS annotations on @Compensate/@Complete methods

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3073?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3073: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.jboss.org/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|http://example.com]: > It is up to the implementation on how the Compensate methods are called. > This could be through JAX-RS calls but this should not be the only way (although an implementation will probably only implement one method). This makes it easier to use the 'events' way of coordination. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3090) LRA TCK failures need to report more context to facilitate debugging

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3090?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3090: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > LRA TCK failures need to report more context to facilitate debugging > -------------------------------------------------------------------- > > Key: JBTM-3090 > URL: https://issues.jboss.org/browse/JBTM-3090 > 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 > > > The TCK test failure message reports > > failures.forEach(f -> System.out.printf("%s%n", f)); > where f is the failure reason. There is also a verbose option which prints out the stack trace where the failure was reported. But in some failure cases these two pieces of information are insufficient to debug the failure. It would be nice if the resources that participated in the test also logged information which could be reported for more effective analysis of the reasons for the failure. This last requirement may affect the TCK itself so the code in the eclipse microprofile-lra repo should be analysed as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3089?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3089: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > LRA code improvements > --------------------- > > Key: JBTM-3089 > URL: https://issues.jboss.org/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.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3105) STM TaxonomyTest failure

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3105?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3105: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > STM TaxonomyTest failure > ------------------------ > > Key: JBTM-3105 > URL: https://issues.jboss.org/browse/JBTM-3105 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: STM > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There was test failure during a CI PR test: testIsClosedNestedParentNotVisible(org.jboss.stm.TaxonomyTest) on job > http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-narayana-cately... -- 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 Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3116?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3116: ----------------------------------- Fix Version/s: 5.next (was: 5.9.5.Final) > 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-3069) XTS over SSL Quickstart failed

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3069?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3069: ----------------------------------- Fix Version/s: 5.next > XTS over SSL Quickstart failed > ------------------------------ > > Key: JBTM-3069 > URL: https://issues.jboss.org/browse/JBTM-3069 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing, XTS > Reporter: Amos Feng > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3070) Quickstart for transaction driver should not be using reflection

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3070?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3070: ----------------------------------- Fix Version/s: 5.next > Quickstart for transaction driver should not be using reflection > ---------------------------------------------------------------- > > Key: JBTM-3070 > URL: https://issues.jboss.org/browse/JBTM-3070 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > Currently the quickstart of transaction driver standalone uses reflection for forcibly closing H2 connection. It was used as a way to overcome the H2 issues with XA connection. > As the quickstart tests recovery it arbitrary throws an exception. This makes issue for H2 as it consider the connection as unfinished but if we close it it does not care and sets autocommit to true and let all the changes being immediately propagated to database. > That's what we don't want as we test recovery and we expect recovery to finish the in-doubt data. > The issue is only for H2 behaviour. "Normal" databases as PostgreSQL makes checks on unfinished transaction in jdbc driver and their decisions are based on it. > Nevertheless using reflection is not a good habit and it's a hacky. For quickstarts it should not be the case. There needs to be a way how to avoid it. -- 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