April 2020 - jbossts-issues - Jboss List Archives

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3229?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3229: ----------------------------------- Fix Version/s: 5.next > 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: Blocker > Fix For: 5.next > > > 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)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3239) Failing AfterLRA participant calls are not repeated with recovery module

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3239?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3239: ----------------------------------- Fix Version/s: 5.next > Failing AfterLRA participant calls are not repeated with recovery module > ------------------------------------------------------------------------ > > Key: JBTM-3239 > URL: https://issues.redhat.com/browse/JBTM-3239 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > The afterLRA calls are currently delivered only twice when the LRA is finished (twice because of JBTM-3163). When these two calls fail the afterLRA call is never repeated again. However, the specification states that afterLRA must be repeated until the 200 status code is returned. > The main reason for this issue is the handling of afterLRA listeners in the Transaction object which means that the LRA enters the end phase (Closed/Cancelled) then the afterLRA listeners are called (twice because of above-mentioned issue) but if these calls fail there is nothing telling the transaction object to repeat the calls on the recovery. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3280) Some LRA TCK tests fail on CI

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3280?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3280: ---------------------------------- Description: Not reproducible locally so far. Currently we know of: - TckTests#timeLimit - TckRecoveryTests#testCancelWhenParticipantIsRestarted was:Not reproducible locally so far. > Some LRA TCK tests fail on CI > ----------------------------- > > Key: JBTM-3280 > URL: https://issues.redhat.com/browse/JBTM-3280 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Not reproducible locally so far. > Currently we know of: > - TckTests#timeLimit > - TckRecoveryTests#testCancelWhenParticipantIsRestarted -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3280) Some LRA TCK tests fail on CI

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3280?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3280: ---------------------------------- Summary: Some LRA TCK tests fail on CI (was: TckTests$timelimit is failing on CI) > Some LRA TCK tests fail on CI > ----------------------------- > > Key: JBTM-3280 > URL: https://issues.redhat.com/browse/JBTM-3280 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Not reproducible locally so far. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3273) Avoid implementing InvocationHandler in jtaLogger

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3273?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Mayank Kunwar created pull request #1590 in GitHub -------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Avoid implementing InvocationHandler in jtaLogger > ------------------------------------------------- > > Key: JBTM-3273 > URL: https://issues.redhat.com/browse/JBTM-3273 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: JTA > Reporter: Sanne Grinovero > Assignee: Mayank Kunwar > Priority: Major > > Context: optimisations for Quarkus > Class {{com.arjuna.ats.jta.logging.jtaLogger}} is implementing {{InvocationHandler}}, and this is causing some difficulties in optimising Narayana for GraalVM native images. > One problem is that all classes which use the logger have access to the {{InvocationHandler}}, which makes the analysis phase of the compiler quite more complex; this gets confusing when there is a compilation failure as this gets occasionally reported as the root cause (even though it's just one of the paths leading to a non-real issue). > A secondary problem is that this class is inizializing a rather expensive proxy; this is less important but it would be great for the sake of bootstrap optimisations to refactor the {{i18NLogger}} field to not be a proxy. > See also https://github.com/quarkusio/quarkus/pull/5343 : with such invocation handlers being widely reachable, it's very hard to support its native compilation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3281) Forget should be called for nested participant when the parent LRA is closed

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3281?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3281: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1591 > Forget should be called for nested participant when the parent LRA is closed > ---------------------------------------------------------------------------- > > Key: JBTM-3281 > URL: https://issues.redhat.com/browse/JBTM-3281 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > The TCK test {{TckContextTests.testForgetCalledForNestedParticipantsWhenParentIsClosed}} is currently failing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3282) LRA quickstarts lra-examples wrongly re-compile coordinator

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3282?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3282: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/quickstart/pull/274 > LRA quickstarts lra-examples wrongly re-compile coordinator > ----------------------------------------------------------- > > Key: JBTM-3282 > URL: https://issues.redhat.com/browse/JBTM-3282 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Affects Versions: 5.10.4.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The LRA quickstarts 'lra-examples' tries to recompile the LRA coordinator. > This is wrong as LRA coordinator should be shipped and used as it is in the version provided by Narayana team. > This recompilation causes the issue when there is a non-existing version of LRA API spec in the repo (e.g. some snapshot from eclipse microprofile). > Resolution: > The coordinator should be taken from maven repository as provided during the Narayana release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3282) LRA quickstarts lra-examples wrongly re-compile coordinator

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3282: -------------------------------------- Summary: LRA quickstarts lra-examples wrongly re-compile coordinator Key: JBTM-3282 URL: https://issues.redhat.com/browse/JBTM-3282 Project: JBoss Transaction Manager Issue Type: Bug Components: Quickstarts Affects Versions: 5.10.4.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka The LRA quickstarts 'lra-examples' tries to recompile the LRA coordinator. This is wrong as LRA coordinator should be shipped and used as it is in the version provided by Narayana team. This recompilation causes the issue when there is a non-existing version of LRA API spec in the repo (e.g. some snapshot from eclipse microprofile). Resolution: The coordinator should be taken from maven repository as provided during the Narayana release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3278) Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272)

by Martin Stefanko (Jira)

[ https://issues.redhat.com/browse/JBTM-3278?page=com.atlassian.jira.plugin... ] Martin Stefanko updated JBTM-3278: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1588 > Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272) > ------------------------------------------------------------------------------------ > > Key: JBTM-3278 > URL: https://issues.redhat.com/browse/JBTM-3278 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > LRA issue 272 - https://github.com/eclipse/microprofile-lra/issues/272 > We must require (fail the deployment otherwise) that LRA method must be combined with either Compensate method or AfterLRA method in the same LRA resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3281) Forget should be called for nested participant when the parent LRA is closed

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3281: ------------------------------------- Summary: Forget should be called for nested participant when the parent LRA is closed Key: JBTM-3281 URL: https://issues.redhat.com/browse/JBTM-3281 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.3.Final Reporter: Martin Stefanko Assignee: Martin Stefanko The TCK test {{TckContextTests.testForgetCalledForNestedParticipantsWhenParentIsClosed}} is currently failing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 11 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2020