November 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3186) Safeguard LRA filters for situations when CDI is not available

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3186?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3186: ----------------------------------- Fix Version/s: 5.10.0.Final > Safeguard LRA filters for situations when CDI is not available > --------------------------------------------------------------- > > Key: JBTM-3186 > URL: https://issues.jboss.org/browse/JBTM-3186 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > When CDI is not available in LRA microservice, following exception is thrown: > {code:java} > Caused by: java.lang.NullPointerException > at io.narayana.lra.filter.ServerLRAFilter.filter(ServerLRAFilter.java:311) > {code} > This is thrown because CDI is not available in the container. The check for null injection can prohibit this behavior and LRA can still function for REST-based services in case CDI is not present. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3187) Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3187?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3187. ---------------------------------- > Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type > ----------------------------------------------------------------------------------- > > Key: JBTM-3187 > URL: https://issues.jboss.org/browse/JBTM-3187 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > application/octet-stream is the default media type in RESTEasy which is used when {{@Produces}} value is not specified. We are always expecting {{String}} values from LRA participant methods so instead of requiring {{(a)Produces(MediaType.TEXT_PLAIN)}} on each {{@Compensate}}, {{@Complete}}, {{@Status}}, etc. methods we can include {{MessageBodyWriter<ParticipantStatus>}} implementation in {{narayana-lra}} module which will just transform {{ParticipantStatus}} value to {{String}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3187) Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3187?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3187: ----------------------------------- Fix Version/s: 5.10.0.Final > Add MessageBodyWriter for ParticipantStatus and application/octet-stream media type > ----------------------------------------------------------------------------------- > > Key: JBTM-3187 > URL: https://issues.jboss.org/browse/JBTM-3187 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > application/octet-stream is the default media type in RESTEasy which is used when {{@Produces}} value is not specified. We are always expecting {{String}} values from LRA participant methods so instead of requiring {{(a)Produces(MediaType.TEXT_PLAIN)}} on each {{@Compensate}}, {{@Complete}}, {{@Status}}, etc. methods we can include {{MessageBodyWriter<ParticipantStatus>}} implementation in {{narayana-lra}} module which will just transform {{ParticipantStatus}} value to {{String}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3190) Transform LRA coordinator runtime to Quarkus

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3190?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3190. ---------------------------------- > Transform LRA coordinator runtime to Quarkus > -------------------------------------------- > > Key: JBTM-3190 > URL: https://issues.jboss.org/browse/JBTM-3190 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > [LRA coordinator|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-c...] is an essential part of Narayana LRA processing. It would be beneficial to move the runtime from [Thorntail|https://thorntail.io] to [Quarkus|https://quarkus.io] for faster startup times and better memory utilization. > If possible, one additional step can be to compile lra-coordinator to the native executable which can bump out the performance of the lra-coordinator docker image. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3190) Transform LRA coordinator runtime to Quarkus

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3190?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3190: ----------------------------------- Fix Version/s: 5.10.0.Final > Transform LRA coordinator runtime to Quarkus > -------------------------------------------- > > Key: JBTM-3190 > URL: https://issues.jboss.org/browse/JBTM-3190 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > [LRA coordinator|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-c...] is an essential part of Narayana LRA processing. It would be beneficial to move the runtime from [Thorntail|https://thorntail.io] to [Quarkus|https://quarkus.io] for faster startup times and better memory utilization. > If possible, one additional step can be to compile lra-coordinator to the native executable which can bump out the performance of the lra-coordinator docker image. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3191) Align LRA client expectations for LRA coordinator default port

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3191?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3191. ---------------------------------- > Align LRA client expectations for LRA coordinator default port > -------------------------------------------------------------- > > Key: JBTM-3191 > URL: https://issues.jboss.org/browse/JBTM-3191 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > LRA coordinator by default starts at port 8080, however, LRA client expects it by default at 8082. This force even very simple applications to specify {{lra.http.port}} which seems unnecessary. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3191) Align LRA client expectations for LRA coordinator default port

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3191?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3191: ----------------------------------- Fix Version/s: 5.10.0.Final > Align LRA client expectations for LRA coordinator default port > -------------------------------------------------------------- > > Key: JBTM-3191 > URL: https://issues.jboss.org/browse/JBTM-3191 > Project: JBoss Transaction Manager > Issue Type: Bug > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.10.0.Final > > > LRA coordinator by default starts at port 8080, however, LRA client expects it by default at 8082. This force even very simple applications to specify {{lra.http.port}} which seems unnecessary. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3180?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3180. ---------------------------------- > 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 > Fix For: 5.10.0.Final > > > 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.13.8#713008)

5 years

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3180?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3180: ----------------------------------- Fix Version/s: 5.10.0.Final > 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 > Fix For: 5.10.0.Final > > > 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.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2652) Include STM javadocs on narayana.io

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2652?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2652. ---------------------------------- > Include STM javadocs on narayana.io > ----------------------------------- > > Key: JBTM-2652 > URL: https://issues.jboss.org/browse/JBTM-2652 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation, STM > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > > Should be part of http://narayana.io/docs/api/index.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 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 November 2019