June 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2685) Check that narayana builds and runs using the Java SE 9 compiler

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2685?page=com.atlassian.jira.plugin.... ] Tom Jenkinson reassigned JBTM-2685: ----------------------------------- Assignee: Amos Feng (was: Michael Musgrove) > Check that narayana builds and runs using the Java SE 9 compiler > ---------------------------------------------------------------- > > Key: JBTM-2685 > URL: https://issues.jboss.org/browse/JBTM-2685 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Build System > Affects Versions: 5.3.3.Final > Reporter: Michael Musgrove > Assignee: Amos Feng > Priority: Critical > > **(some commits that reference this issue are actually for https://issues.jboss.org/browse/JBTM-2955)** > Get the latest build from https://jdk9.java.net/download/ and check for any issues. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3038?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3038: ----------------------------------- Description: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: {code}  <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>checkstyle-config</artifactId> <version>1</version> </dependency> {code} Note that thorntail and wildfly appear to use the same ruleset. was: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: {code}  <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>checkstyle-config</artifactId> <version>1</version> </dependency> {code} > Include the checkstyle plugin in LRA maven poms > ----------------------------------------------- > > Key: JBTM-3038 > URL: https://issues.jboss.org/browse/JBTM-3038 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. > Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: > {code} >  > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>checkstyle-config</artifactId> > <version>1</version> > </dependency> > {code} > Note that thorntail and wildfly appear to use the same ruleset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3034: ---------------------------------- Forum Reference: https://developer.jboss.org/message/983627#983627 > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3034 > URL: https://issues.jboss.org/browse/JBTM-3034 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.8.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3034) CMR recovery wrongly handles commit and rollback

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-3034?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-3034: --------------------------------------- After more investigation I found the observed issues is the same in all cases. The CMR which is committed then causes the resource is called to be rolled-back too. The regression seems to be caused by the fact that the {{XAResource}} is withdrawn from the {{XAResourceRecord}} https://github.com/jbosstm/narayana/blob/5.8.2.Final/ArjunaJTA/jta/classe... during recovery (in second phase by {{AtomicActionRecoveryModule}}) and the {{_xidScans}} is not updated with that fact (https://github.com/jbosstm/narayana/blob/5.8.2.Final/ArjunaJTA/jta/classe...). This was done intentionally for {{XATerminator}} recovery does not add warnings {{noxaresource}} (https://github.com/jbosstm/narayana/pull/1059/files#diff-8487f43e773b3321...) but it seems not correct from CMR point of view. > CMR recovery wrongly handles commit and rollback > ------------------------------------------------- > > Key: JBTM-3034 > URL: https://issues.jboss.org/browse/JBTM-3034 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.8.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > The recovery of CMR works wrongly. > For scenario I currently investigate there is issue the second resource beging committed and rolled-back too. > # cmr resource prepare (no real action on the local transction) > # xa resource prepare (prepared in real as XA) > # cmr resource commit (commiting the local transaction) > # JVM crash > # expecting the xa resource being committed, but it's committed and immediatelly rolled-back. fortunatelly it seems it does not causes data consistency issue. > This is similar to what was seen in issue https://issues.jboss.org/browse/JBEAP-6326 but not the same. The seems could be connected with fix for https://issues.jboss.org/browse/JBTM-2734. More investigation is needed. > This is *regression* against EAP 7.0.0. The same scenario works in 7.0.0 smoothly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3038?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3038: ----------------------------------- Description: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: {code}  <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>checkstyle-config</artifactId> <version>1</version> </dependency> {code} was: To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from those projects. > Include the checkstyle plugin in LRA maven poms > ----------------------------------------------- > > Key: JBTM-3038 > URL: https://issues.jboss.org/browse/JBTM-3038 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. > Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from one of those projects. For example, thorntail uses: > {code} >  > <dependency> > <groupId>org.wildfly.swarm</groupId> > <artifactId>checkstyle-config</artifactId> > <version>1</version> > </dependency> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3038) Include the checkstyle plugin in LRA maven poms

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3038: -------------------------------------- Summary: Include the checkstyle plugin in LRA maven poms Key: JBTM-3038 URL: https://issues.jboss.org/browse/JBTM-3038 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.8.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Priority: Optional Fix For: 5.next To achieve a level of consistency of code it would be advantageous to include a formal set of checkstyle rules in this project. Since a primary user of the LRA coordinator and LRA APIs are microprofile-lra and thorntail it makes sense to use the ruleset from those projects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3037) LRA context is not always removed if the LRA is ended

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3037: -------------------------------------- Summary: LRA context is not always removed if the LRA is ended Key: JBTM-3037 URL: https://issues.jboss.org/browse/JBTM-3037 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.8.2.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The following scenario leaves the LRA context still current: start an LRA call a service annotated with, for example, {code} @LRA(value = LRA.Type.REQUIRED, cancelOn = {Response.Status.NOT_FOUND}) {/code} If the invoked method returns the NOT_FOUND status then the LRA is automatically terminated. When the request returns to the client there should be no current LRA context active. The issue here is that the next request that the client makes may still have the old LRA still associated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3035) LRA context should propagate across non-LRA aware services

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3035?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3035: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1335, https://github.com/eclipse/microprofile-lra/pull/10 (was: https://github.com/jbosstm/narayana/pull/1335) > LRA context should propagate across non-LRA aware services > ---------------------------------------------------------- > > Key: JBTM-3035 > URL: https://issues.jboss.org/browse/JBTM-3035 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > If you have a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and this calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3035) LRA context should propagate across non-LRA aware services

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3035?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3035: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done The associated spec PR is https://github.com/eclipse/microprofile-lra/pull/10 > LRA context should propagate across non-LRA aware services > ---------------------------------------------------------- > > Key: JBTM-3035 > URL: https://issues.jboss.org/browse/JBTM-3035 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > If you have a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and this calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3035) LRA context should propagate across non-LRA aware services

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3035?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3035: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1335 > LRA context should propagate across non-LRA aware services > ---------------------------------------------------------- > > Key: JBTM-3035 > URL: https://issues.jboss.org/browse/JBTM-3035 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.8.2.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > If you have a microservice A that wants to participate in an LRA and calls microservice B (which does not have specific LRA behaviour) and this calls microservice C (which does have specific LRA behaviour), then B should not need to be annotated with @LRA. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 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 June 2018