December 2019 - jbossts-issues - Jboss List Archives

[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.10.1.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.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3102) Provide a gRPC service for accessing OTS funtionality

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3102?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3102: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Provide a gRPC service for accessing OTS funtionality > ----------------------------------------------------- > > Key: JBTM-3102 > URL: https://issues.jboss.org/browse/JBTM-3102 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > JTS was the Java EE standard for different JTA implementations to interoperate. Since CORBA (and therefore JTS) is now an optional component of Jakarta EE there is a need for an alternative specification for how services can propagate a transaction context. A popular alternative to CORBA is gRPC which has the following nice features: 1) it is a good technology choice for service to service interactions; 2) is polyglot or, as stated in the documentation, "Automatically generates idiomatic client and server stubs for your service in a variety of languages and platforms"; and 3) provides excellent performance. > The reason JTS was chosen as the Java EE interop standard is that 1) it provides language level bindings that enable interoperability; and 2) it builds on a pre-existing industry standard, namely OTS. > Consequently, it is reasonable to conclude that a mapping from CosTransactions.idl (the IDL definition for OTS) to Protocol Buffers and gRPC services will: > - Enable existing OTS/JTS implementations to provide service in these new environments. > - Enable new and existing gRPC services to be able to access transactional functionality in an interoperable manner. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3103) LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3103?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3103: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > LRA api-particpant quickstart needs aligning with the latest MP LRA spec changes > -------------------------------------------------------------------------------- > > Key: JBTM-3103 > URL: https://issues.jboss.org/browse/JBTM-3103 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > This quickstart depends on LRAParticipantDeserializer to recreate participants during crash recovery but [MP LRA issue #61|https://github.com/eclipse/microprofile-lra/issues/61] has removed this class. The alternative registration mechanism is still outstanding [see the comments on issue #35|https://github.com/eclipse/microprofile-lra/issues/35] for a discussion of the new way of registering participants. > Until a PR is raised for this issue I would like to disable the quickstarts that utilise LRAParticipantDeserializer. > Note that this has only just become an issue since previouslythe Narayana implementation of LRA depended on a specific snapshot build in the eclipse repo (since the LRA spec is in flux), but snapshots are purged after a month so the old way of registering participants is no longer available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3108) Renable the maven site plugin for the LRA module

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3108?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3108: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Renable the maven site plugin for the LRA module > ------------------------------------------------ > > Key: JBTM-3108 > URL: https://issues.jboss.org/browse/JBTM-3108 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Issue https://issues.jboss.org/browse/JBTM-3093 disabled the site plugin while the MP LRA APIs are still being developed. When MP LRA releases we need to renable the site plugin (used for code coverage tests). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3225) Decide whether we should make the internal LRA client API not auto closable

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3225?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3225: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Decide whether we should make the internal LRA client API not auto closable > --------------------------------------------------------------------------- > > Key: JBTM-3225 > URL: https://issues.jboss.org/browse/JBTM-3225 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The LRA implementation contains an internal client API called io.narayana.lra.client.NarayanaLRAClient which implements java.io.Closeable. A recent PR (see issue https://issues.jboss.org/browse/JBTM-3212) made the implementation of the close method a NOOP (since there is no longer any need for cleanup actions). But the method was left empty since there is a possibility that is will be needed in LRA version 1.x where a LRA client API will be added and since there are existing users of the client API. > This task is a reminder to revisit the decision to remove java.io.Closeable prior to releasing an implementation of [version 1.0 of the LRA specification|https://github.com/eclipse/microprofile-lra/issues?q=is%3Ao...]. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3204) Upgrade LRA TCK recovery handling to accommodate specification changes

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3204?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3204: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Upgrade LRA TCK recovery handling to accommodate specification changes > ----------------------------------------------------------------------- > > Key: JBTM-3204 > URL: https://issues.jboss.org/browse/JBTM-3204 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > LRA TCK added a new way of handling LRA recovery in https://github.com/eclipse/microprofile-lra/commit/52b799768b3d0fa1746f2b.... Update the implementation to accommodate these changes. > Also update the LRA versions to the latest snapshots: > <version.microprofile.lra.api>1.0-20190927.061209-550</version.microprofile.lra.api> > <version.microprofile.lra.tck>1.0-20190927.061211-550</version.microprofile.lra.tck> > diff: [https://github.com/eclipse/microprofile-lra/compare/1.0-RC1...fab960eede3...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3213) Ensure the LRA module is configurable

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3213?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3213: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Ensure the LRA module is configurable > -------------------------------------- > > Key: JBTM-3213 > URL: https://issues.jboss.org/browse/JBTM-3213 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There are some LRA parameters that we would like to be configurable (timeouts and thread pools for example). Since LRA is a microprofile spec we should leverage microprofile-config for this purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3223) Validate LRA behaviour when multiple LRA's are active on the same thread

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3223?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3223: ----------------------------------- Fix Version/s: 5.next (was: 5.10.1.Final) > Validate LRA behaviour when multiple LRA's are active on the same thread > ------------------------------------------------------------------------- > > Key: JBTM-3223 > URL: https://issues.jboss.org/browse/JBTM-3223 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add tests that check that when multiple LRA's are active on the same thread that as one LRA finishes that: > - the next one is handled correctly > - creating another one still works fine > This issues relates to some suspect code at the end of the method `NarayanaLRAClient#endLRA` where the base URI of the target coordinator includes the Uid part of the LRA id. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3216) Narrow the default recovery configuration in the jbossts-properties.xml files

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3216?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3216: ----------------------------------- Fix Version/s: 5.next > Narrow the default recovery configuration in the jbossts-properties.xml files > ----------------------------------------------------------------------------- > > Key: JBTM-3216 > URL: https://issues.jboss.org/browse/JBTM-3216 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Configuration, JTA, JTS > Affects Versions: 5.10.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > Fix For: 5.next > > > There is default configuration for Narayana provided in XML files {{jbossts-properties.xml}}. They are part of the released jar files (they can be found at `META-INF` directory). > These configuration files are different depending on the artifact. For example configuration defined in {{jbossts-properties.xml}} for JTS is different from JTA version - e.g. recovery modules are different and so. > The configurations should be a bit narrowed to use better defaults. The discussion about this topic is at https://developer.jboss.org/message/991332 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3212) Ensure that an LRA timeout timer is restarted after a crash

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3212?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3212: ----------------------------------- Fix Version/s: 5.next > Ensure that an LRA timeout timer is restarted after a crash > ----------------------------------------------------------- > > Key: JBTM-3212 > URL: https://issues.jboss.org/browse/JBTM-3212 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > LRAs can be timed out. After a crash the time should be restarted. Currently this functionality is marked as a TODO item: > > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... > and > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 4 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