April 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2411) Investigate jgroups-raft and whether this can help with cloud object store

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-2411?page=com.atlassian.jira.plugin... ] Mayank Kunwar reassigned JBTM-2411: ----------------------------------- Assignee: Mayank Kunwar > Investigate jgroups-raft and whether this can help with cloud object store > -------------------------------------------------------------------------- > > Key: JBTM-2411 > URL: https://issues.redhat.com/browse/JBTM-2411 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Recovery, Transaction Core > Reporter: Thomas Jenkinson > Assignee: Mayank Kunwar > Priority: Major > Fix For: 5.next > > > http://belaban.blogspot.ch/2015/05/release-of-jgroups-raft-02.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

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

by Mayank Kunwar (Jira)

[ https://issues.redhat.com/browse/JBTM-3273?page=com.atlassian.jira.plugin... ] Mayank Kunwar reassigned JBTM-3273: ----------------------------------- Assignee: Mayank Kunwar (was: Ondrej Chaloupka) > 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)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3073?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3073: ----------------------------------- Status: Resolved (was: Pull Request Sent) Assignee: Martin Stefanko (was: Michael Musgrove) Resolution: Done > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.redhat.com/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Blocker > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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.13.8#713008)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3073?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3073: ---------------------------------------- This issue was fixed whilst fixing issue JBTM-3087 > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.redhat.com/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: Blocker > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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.13.8#713008)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3073?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3073: ---------------------------------------- This issue was fixed as a side effect of the fix for issue JBTM-3087 > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.redhat.com/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: Blocker > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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.13.8#713008)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3073?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3073: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1450 > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.redhat.com/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: Blocker > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3182) Fix basic LRA tests

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3182?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3182: ----------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/jbosstm/narayana/pull/1490 > Fix basic LRA tests > ------------------- > > Key: JBTM-3182 > URL: https://issues.redhat.com/browse/JBTM-3182 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > Fix For: 5.9.8.Final > > > lra-test/basic is unable to run because of wrong CDI configuration after latest LRA upgrade: > {code:java} > ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002025: Unknown exception while executing GET /root/participant/lra: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3182) Fix basic LRA tests

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3182?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3182: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix basic LRA tests > ------------------- > > Key: JBTM-3182 > URL: https://issues.redhat.com/browse/JBTM-3182 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > Fix For: 5.9.8.Final > > > lra-test/basic is unable to run because of wrong CDI configuration after latest LRA upgrade: > {code:java} > ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default task-1) RESTEASY002025: Unknown exception while executing GET /root/participant/lra: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3073?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3073: ----------------------------------- Description: Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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. was: 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. > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.redhat.com/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: Blocker > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|https://github.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.13.8#713008)

4 years

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: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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 > > 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)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2020