June 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3311) JMH upgrade and code refactor

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3311?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3311: ----------------------------------- Status: Pull Request Sent (was: Open) > JMH upgrade and code refactor > ----------------------------- > > Key: JBTM-3311 > URL: https://issues.redhat.com/browse/JBTM-3311 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Reporter: Mayank Kunwar > Assignee: Mayank Kunwar > Priority: Major > > This JIRA is for updating JMH to its latest version (i.e. 1.23) and code refactoring. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3330) Nested closed LRA is kept in Closing state which is breaking the LRA state model

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3330: ------------------------------------- Summary: Nested closed LRA is kept in Closing state which is breaking the LRA state model Key: JBTM-3330 URL: https://issues.redhat.com/browse/JBTM-3330 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.4.Final Reporter: Martin Stefanko The closed nested LRA is kept in the Closing state until the parent closes/cancels. This is against the the LRA state model - https://github.com/eclipse/microprofile-lra/blob/master/spec/src/main/asc... where only transition from Closed to Cancelling is allowed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3320) LRA forget calls for nested completed participants are not repeated and do not close the LRA

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3320?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3320: ----------------------------------- Fix Version/s: 5.next > LRA forget calls for nested completed participants are not repeated and do not close the LRA > -------------------------------------------------------------------------------------------- > > Key: JBTM-3320 > URL: https://issues.redhat.com/browse/JBTM-3320 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.5.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > forgetAllParticipants does not repeat failed forget calls and if the calls are successful the nested LRA is not finished. This leaves the nested LRA active. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3328) Possibly unneccessary logging on XA endAssociation

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3328?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3328: ----------------------------------- Fix Version/s: 5.next > Possibly unneccessary logging on XA endAssociation > -------------------------------------------------- > > Key: JBTM-3328 > URL: https://issues.redhat.com/browse/JBTM-3328 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.10.5.Final > Reporter: Vladimir Kuruc > Priority: Major > Fix For: 5.next > > Attachments: narayana-spring-boot-xa-end.zip > > > In my project with Spring Boot, Hibernate, Informix, DBCP pool Narayana logs unnecessarily XA endAssociation. In the attached sample project I can prove it with the embedded Derby database. This happens during a rollback transaction. According to the linked discussion forum, this is due to [commit|https://github.com/jbosstm/narayana/commit/fcfb851072ea28c80902710...] and the solution would be to log only with duplicate resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3328) Possibly unneccessary logging on XA endAssociation

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3328?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3328: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Possibly unneccessary logging on XA endAssociation > -------------------------------------------------- > > Key: JBTM-3328 > URL: https://issues.redhat.com/browse/JBTM-3328 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.10.5.Final > Reporter: Vladimir Kuruc > Priority: Major > Attachments: narayana-spring-boot-xa-end.zip > > > In my project with Spring Boot, Hibernate, Informix, DBCP pool Narayana logs unnecessarily XA endAssociation. In the attached sample project I can prove it with the embedded Derby database. This happens during a rollback transaction. According to the linked discussion forum, this is due to [commit|https://github.com/jbosstm/narayana/commit/fcfb851072ea28c80902710...] and the solution would be to log only with duplicate resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3329) Add supportNested alternative for LRA methods

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3329: ------------------------------------- Summary: Add supportNested alternative for LRA methods Key: JBTM-3329 URL: https://issues.redhat.com/browse/JBTM-3329 Project: JBoss Transaction Manager Issue Type: Enhancement Components: LRA Affects Versions: 5.10.4.Final Reporter: Martin Stefanko Assignee: Martin Stefanko Add something similar to @LRA(supportNested=false) for LRA participant to test out the inclusion of this API in the specification. Possibly something like new annotation @TopLevelLRAParticipant that can be placed on LRA participant class. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3328) Possibly unneccessary logging on XA endAssociation

by Vladimir Kuruc (Jira)

[ https://issues.redhat.com/browse/JBTM-3328?page=com.atlassian.jira.plugin... ] Vladimir Kuruc updated JBTM-3328: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1633 > Possibly unneccessary logging on XA endAssociation > -------------------------------------------------- > > Key: JBTM-3328 > URL: https://issues.redhat.com/browse/JBTM-3328 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: JTA > Affects Versions: 5.10.5.Final > Reporter: Vladimir Kuruc > Priority: Major > Attachments: narayana-spring-boot-xa-end.zip > > > In my project with Spring Boot, Hibernate, Informix, DBCP pool Narayana logs unnecessarily XA endAssociation. In the attached sample project I can prove it with the embedded Derby database. This happens during a rollback transaction. According to the linked discussion forum, this is due to [commit|https://github.com/jbosstm/narayana/commit/fcfb851072ea28c80902710...] and the solution would be to log only with duplicate resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3328) Possibly unneccessary logging on XA endAssociation

by Vladimir Kuruc (Jira)

Vladimir Kuruc created JBTM-3328: ------------------------------------ Summary: Possibly unneccessary logging on XA endAssociation Key: JBTM-3328 URL: https://issues.redhat.com/browse/JBTM-3328 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.10.5.Final Reporter: Vladimir Kuruc Attachments: narayana-spring-boot-xa-end.zip In my project with Spring Boot, Hibernate, Informix, DBCP pool Narayana logs unnecessarily XA endAssociation. In the attached sample project I can prove it with the embedded Derby database. This happens during a rollback transaction. According to the linked discussion forum, this is due to [commit|https://github.com/jbosstm/narayana/commit/fcfb851072ea28c80902710...] and the solution would be to log only with duplicate resources. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3327) Update Quarkus to 1.5.0.Final

by Anonymous (Jira)

[ https://issues.redhat.com/browse/JBTM-3327?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Martin Stefanko created pull request #1632 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Update Quarkus to 1.5.0.Final > ----------------------------- > > Key: JBTM-3327 > URL: https://issues.redhat.com/browse/JBTM-3327 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > We are still shipping LRA coordinator with Quarkus 0.22.0 which is quite outdated. I would suggest upgrading. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3327) Update Quarkus to 1.5.0.Final

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3327: ------------------------------------- Summary: Update Quarkus to 1.5.0.Final Key: JBTM-3327 URL: https://issues.redhat.com/browse/JBTM-3327 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.10.4.Final Reporter: Martin Stefanko Assignee: Martin Stefanko We are still shipping LRA coordinator with Quarkus 0.22.0 which is quite outdated. I would suggest upgrading. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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