August 2019 - jbossts-issues - Jboss List Archives

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

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3182?page=com.atlassian.jira.plugin.... ] Work on JBTM-3182 started by Martin Stefanko. --------------------------------------------- > Fix basic LRA tests > ------------------- > > Key: JBTM-3182 > URL: https://issues.jboss.org/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: Major > > 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.12.1#712002)

5 years, 4 months

1
0
0 / 0

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

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3182: ------------------------------------- Summary: Fix basic LRA tests Key: JBTM-3182 URL: https://issues.jboss.org/browse/JBTM-3182 Project: JBoss Transaction Manager Issue Type: Bug Reporter: Martin Stefanko Assignee: Martin Stefanko 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.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3159) LRA does not work for JAX-RS resources which are not root resource classes

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3159?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3159: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.9.6.Final Resolution: Done > LRA does not work for JAX-RS resources which are not root resource classes > -------------------------------------------------------------------------- > > Key: JBTM-3159 > URL: https://issues.jboss.org/browse/JBTM-3159 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.5.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.9.6.Final > > > When JAX-RS LRA participant is not a root resource class the compensation/completion methods are not called because the constructed path is taken from the string value of the root resource @Path annotation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3181) lra-proxy-api is not deployed to Nexus during release

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3181?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka updated JBTM-3181: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1489 > lra-proxy-api is not deployed to Nexus during release > ----------------------------------------------------- > > Key: JBTM-3181 > URL: https://issues.jboss.org/browse/JBTM-3181 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > Artifact `lra-proxy-api` is not (and it has never been) deployed at Nexus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3181) lra-proxy-api is not deployed to Nexus during release

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3181?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Ondrej Chaloupka created pull request #1489 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > lra-proxy-api is not deployed to Nexus during release > ----------------------------------------------------- > > Key: JBTM-3181 > URL: https://issues.jboss.org/browse/JBTM-3181 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > Artifact `lra-proxy-api` is not (and it has never been) deployed at Nexus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3181) lra-proxy-api is not deployed to Nexus during release

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3181: -------------------------------------- Summary: lra-proxy-api is not deployed to Nexus during release Key: JBTM-3181 URL: https://issues.jboss.org/browse/JBTM-3181 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.9.7.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka Fix For: 5.next Artifact `lra-proxy-api` is not (and it has never been) deployed at Nexus. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3180) LRARecord http compliance: Entity null for PUT

by Paul Parkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3180?page=com.atlassian.jira.plugin.... ] Paul Parkinson updated JBTM-3180: --------------------------------- Issue Type: Bug (was: Feature Request) > LRARecord http compliance: Entity null for PUT > ---------------------------------------------- > > Key: JBTM-3180 > URL: https://issues.jboss.org/browse/JBTM-3180 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Paul Parkinson > Assignee: Michael Musgrove > Priority: Minor > > LRARecord has... > case "javax.ws.rs.PUT": > return asyncInvoker.put(Entity.text(null)); > whereas entity should never be null for PUT > I see this comment has been there since the code was first added and so perhaps this is the desired... > // return asyncInvoker.put(Entity.entity(compensatorData, mediaType)); > If not perhaps simply Entity.text("") should suffice (and has in my tests). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3180) LRARecord http compliance: Entity null for PUT

by Paul Parkinson (Jira)

Paul Parkinson created JBTM-3180: ------------------------------------ Summary: LRARecord http compliance: Entity null for PUT Key: JBTM-3180 URL: https://issues.jboss.org/browse/JBTM-3180 Project: JBoss Transaction Manager Issue Type: Feature Request Components: LRA Affects Versions: 5.9.7.Final Reporter: Paul Parkinson Assignee: Michael Musgrove LRARecord has... case "javax.ws.rs.PUT": return asyncInvoker.put(Entity.text(null)); whereas entity should never be null for PUT I see this comment has been there since the code was first added and so perhaps this is the desired... // return asyncInvoker.put(Entity.entity(compensatorData, mediaType)); If not perhaps simply Entity.text("") should suffice (and has in my tests). -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Thomas Jenkinson updated JBTM-741: ---------------------------------- Fix Version/s: 5.next (was: 5.9.7.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Priority: Minor > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1107) Recovery Support in Compensation API

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-1107: ----------------------------------- Fix Version/s: 5.next (was: 5.9.7.Final) > Recovery Support in Compensation API > ------------------------------------ > > Key: JBTM-1107 > URL: https://issues.jboss.org/browse/JBTM-1107 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Compensations > Reporter: Thomas Jenkinson > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > *Background* > Currently Compensations API cannot handle system failures. Transaction state is not persisted in any stage. Thus no handlers will be invoked in case of the system crash. > *Requirements* > # Make handlers persistable (CompensationHandler, ConfirmationHandler, TransactionLoggedHandler). > ## Require Serializable interface. > ## Create PersistableHandler interface (similar to PersistableParticipant in RTS integration). > # Make participant persistable (ParticipantImpl, LocalParticipant, RemoteParticipant). > ## Make transaction identifier persistable (converting it to String should work). > ## Implement PersistableParticipant in ParticipantImpl. > ## Investigate if PARTICIPANT_COUNTERS in ParticipatnImpl have to be updated. > # Make compensation scoped beans persistable. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues August 2019