October 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3046: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3195) CacheStore failed a read_committed check in CI

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3195: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > CacheStore failed a read_committed check in CI > ---------------------------------------------- > > Key: JBTM-3195 > URL: https://issues.jboss.org/browse/JBTM-3195 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > The test hung because of an assertion failing before the threads were all joined: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/tests/c... > No state found while trying to read 0:ffffac110012:863a:5d7bfbf4:11 > Thread for 0:ffffac110012:863a:5d7bfbf4:11 failed > Was in the output (no other errors) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3212) Ensure that an LRA timeout timer is restarted after a crash

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3212?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3212: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Ensure that an LRA timeout timer is restarted after a crash > ----------------------------------------------------------- > > Key: JBTM-3212 > URL: https://issues.jboss.org/browse/JBTM-3212 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > LRAs can be timed out. After a crash the time should be restarted. Currently this functionality is marked as a TODO item: > > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... > and > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3197) Include an STM quickstart running on Quarkus (including native mode)

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3197?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3197: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Include an STM quickstart running on Quarkus (including native mode) > -------------------------------------------------------------------- > > Key: JBTM-3197 > URL: https://issues.jboss.org/browse/JBTM-3197 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator, Quickstarts, STM > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a quickstart that shows how to create an STM example running on Quarkus. The quickstart should also include instructions for building a native executable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3213) Ensure the LRA module is configurable

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3213?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3213: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Ensure the LRA module is configurable > -------------------------------------- > > Key: JBTM-3213 > URL: https://issues.jboss.org/browse/JBTM-3213 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > There are some LRA parameters that we would like to be configurable (timeouts and thread pools for example). Since LRA is a microprofile spec we should leverage microprofile-config for this purpose. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3161) Nested LRA doesn't start in the Spring Boot + JAX-RS application

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3161?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1523 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Nested LRA doesn't start in the Spring Boot + JAX-RS application > ---------------------------------------------------------------- > > Key: JBTM-3161 > URL: https://issues.jboss.org/browse/JBTM-3161 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Critical > Attachments: flight_5.9.6.zip, flight_5.9.8.zip, flight_5.9.8_working.zip > > > For demonstrating purpose, I migrated flight service from [narayana quickstart|https://github.com/jbosstm/quickstart/tree/master/rts/lra/flig...] to the Spring Boot application and uploaded it to the attachment. > When I stop debugger in the original swarm flight service (FlightParticipant [line 64|https://github.com/jbosstm/quickstart/blob/3b848517086c2abc32bff6895b2...]), the *_@HeaderParam(LRA_HTTP_CONTEXT_HEADER) String lraId_*, is new for that service. When I stop debugger in the SpringBoot+JAX-RS, the lraId is the same as for a parent. It looks that the _ServerLRAFilter_ doesn't start the new LRA. > I add a breakpoint to the *_ServerLRAFilter.filter(...)_* to see when the filter is applied and create new LRA before the JAX-RS method. When I call original swarm flight service, the filter is used however when I call SpringBoot flight service, the filter is not used so it looks that the filter is not used at all in the SpringBoot+JAX-RS application. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-2652?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2652: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3214) Add a BeanPopulator method to directly provide a config bean

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3214?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3214: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Add a BeanPopulator method to directly provide a config bean > ------------------------------------------------------------ > > Key: JBTM-3214 > URL: https://issues.jboss.org/browse/JBTM-3214 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Configuration > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Optional > Fix For: 5.next > > > Narayana has quite a flexible mechanism for setting properties: > - it uses xml property files > - it reads Java system properties > - it initialises our config beans using reflection to call the setters > Some systems, Quarkus for example, have their own config mechanisms (MicroProfile Config in the Quarkus example) so it makes sense to allow our beans to be configured directly (avoiding parsing and reflection). > Implementation wise we do already have the PropertiesFactory class to directly provide config properties but that code still uses reflection to set the actual property values and besides, it is an abstract class so we cannot safely add new methods to it. My proposal is to add a single method to the BeanPopulator class: > {code} > public static void setBeanInstance(String name, Object beanInstance) { > beanInstances.putIfAbsent(name, beanInstance); > } > {code} > This code avoids the use of reflection (and possibly xml parsing) whenever access to the named bean is required. Note that this approach requires a user to know in advance which environment beans Narayana is using. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3205) Spring Boot + JAX-RS support

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/JBTM-3205?page=com.atlassian.jira.plugin.... ] Matej Kralik updated JBTM-3205: ------------------------------- Description: I created this enhancement for tracking all issues for Spring Boot + JAX-RS application. {code:xml} ... <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.1.6.RELEASE</version> <relativePath/>  </parent> ... <dependencies>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-jersey</artifactId> </dependency> ... </dependencies> ... {code} was: I created this enhancement for tracking all issues with Spring Boot + JAX-RS application. {code:xml} ... <parent> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>2.1.6.RELEASE</version> <relativePath/>  </parent> ... <dependencies>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-jersey</artifactId> </dependency> ... </dependencies> ... {code} > Spring Boot + JAX-RS support > ---------------------------- > > Key: JBTM-3205 > URL: https://issues.jboss.org/browse/JBTM-3205 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Major > > I created this enhancement for tracking all issues for Spring Boot + JAX-RS application. > {code:xml} > ... > <parent> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-parent</artifactId> > <version>2.1.6.RELEASE</version> > <relativePath/>  > </parent> > ... > <dependencies> >  > <dependency> > <groupId>org.springframework.boot</groupId> > <artifactId>spring-boot-starter-jersey</artifactId> > </dependency> > ... > </dependencies> > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTM-3161) Nested LRA doesn't start in the Spring Boot + JAX-RS application

by Matej Kralik (Jira)

[ https://issues.jboss.org/browse/JBTM-3161?page=com.atlassian.jira.plugin.... ] Matej Kralik commented on JBTM-3161: ------------------------------------ Yes, I meant the [constructor|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-p...]. > Nested LRA doesn't start in the Spring Boot + JAX-RS application > ---------------------------------------------------------------- > > Key: JBTM-3161 > URL: https://issues.jboss.org/browse/JBTM-3161 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Critical > Attachments: flight_5.9.6.zip, flight_5.9.8.zip, flight_5.9.8_working.zip > > > For demonstrating purpose, I migrated flight service from [narayana quickstart|https://github.com/jbosstm/quickstart/tree/master/rts/lra/flig...] to the Spring Boot application and uploaded it to the attachment. > When I stop debugger in the original swarm flight service (FlightParticipant [line 64|https://github.com/jbosstm/quickstart/blob/3b848517086c2abc32bff6895b2...]), the *_@HeaderParam(LRA_HTTP_CONTEXT_HEADER) String lraId_*, is new for that service. When I stop debugger in the SpringBoot+JAX-RS, the lraId is the same as for a parent. It looks that the _ServerLRAFilter_ doesn't start the new LRA. > I add a breakpoint to the *_ServerLRAFilter.filter(...)_* to see when the filter is applied and create new LRA before the JAX-RS method. When I call original swarm flight service, the filter is used however when I call SpringBoot flight service, the filter is not used so it looks that the filter is not used at all in the SpringBoot+JAX-RS application. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 October 2019