November 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3219) Upgrade the RESTEasy dependency to 3.9.1.Final (which matches what WFLY is using)

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3219?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1527 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade the RESTEasy dependency to 3.9.1.Final (which matches what WFLY is using) > --------------------------------------------------------------------------------- > > Key: JBTM-3219 > URL: https://issues.jboss.org/browse/JBTM-3219 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > [WFLY-12786] (Upgrade RESTEasy to 3.9.1.Final) is upgrading its RESTEasy dependency. Since we need to align with WFLY and since we are still on an old beta (from Sept 2016) we should upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3219) Upgrade the RESTEasy dependency to 3.9.1.Final (which matches what WFLY is using)

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3219: -------------------------------------- Summary: Upgrade the RESTEasy dependency to 3.9.1.Final (which matches what WFLY is using) Key: JBTM-3219 URL: https://issues.jboss.org/browse/JBTM-3219 Project: JBoss Transaction Manager Issue Type: Task Components: REST Affects Versions: 5.10.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next [WFLY-12786] (Upgrade RESTEasy to 3.9.1.Final) is upgrading its RESTEasy dependency. Since we need to align with WFLY and since we are still on an old beta (from Sept 2016) we should upgrade. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

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 commented on JBTM-3205: ------------------------------------ [~mmusgrov] Verified. Here are the examples which I mentioned https://github.com/mkralik3/lra-springboot-axon-quickstart For now, it contains two scenarios: * When the original flight service is based on Spring Boot (the logic and endpoints of service are same as original) * When the original hotel service is based on Spring Boot with Axon architecture (Event sourcing + CQRS) (the logic and endpoints of service are same as original) In the future, I would like to add there the third example, which demonstrates more SpringBoot/Axon services which are able to enlist to the coordinator as a participant without REST endpoints. (Using my Axon LRA connector) > 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3218) Transaction statistics for read-only + last record may go wrong

by Ondrej Chaloupka (Jira)

Ondrej Chaloupka created JBTM-3218: -------------------------------------- Summary: Transaction statistics for read-only + last record may go wrong Key: JBTM-3218 URL: https://issues.jboss.org/browse/JBTM-3218 Project: JBoss Transaction Manager Issue Type: Bug Components: JTA Affects Versions: 5.10.0.Final Reporter: Ondrej Chaloupka Assignee: Ondrej Chaloupka As discussed at https://issues.jboss.org/browse/WFTC-78?focusedCommentId=13808486#comment... there was seen a wrong statistics being reported at a remote ejb calls for WFLY. The number of committed transactions went bigger than the number of all processed transactions. This happens when the transaction consists of {{XAResource}} which announces to be read only during {{prepare}} call and with the second resource which is {{LastResource}} (https://github.com/jbosstm/jboss-transaction-spi/blob/master/src/main/jav...). In such case the {{onePhaseCommit}} could be called during the {{BasicAction#prepare}} call (https://github.com/jbosstm/narayana/blob/5.10.0.Final/ArjunaCore/arjuna/c...). In such case the statistics of committed transactions are increased during the {{onePhaseCommit}} method call and then during the {{phase2Commit}} at {{BasicAction#End}} call (https://github.com/jbosstm/narayana/blob/5.10.0.Final/ArjunaCore/arjuna/c...). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3217) Take Compensate and Complete timeout information from the LRA annotation in the same class

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3217?page=com.atlassian.jira.plugin.... ] Martin Stefanko commented on JBTM-3217: --------------------------------------- [~tomjenkinson] I also proposed to just add a label, something like `lra-ready` and then we can revisit when needed but this is aligned with what you said so please go ahead and choose what suits you the best. > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.jboss.org/browse/JBTM-3217 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update the handling of timeout information for Compensate and Complete according to the specification. Now it's defined in the LRA annotation similarly as for the new LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3217) Take Compensate and Complete timeout information from the LRA annotation in the same class

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3217?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson commented on JBTM-3217: ---------------------------------------- I agree that there could be something missing as it is not in our main branch. One option is that we periodically review issues that are Resolved/Done and without a fixVersion to see if they can be merged to master. Another option is we create a separate issue that is something like "Merge LRA branch with master" and target that at 5.next as a blocker (which we would review to see if it can be deferred at the point of 5.next release? > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.jboss.org/browse/JBTM-3217 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update the handling of timeout information for Compensate and Complete according to the specification. Now it's defined in the LRA annotation similarly as for the new LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3217) Take Compensate and Complete timeout information from the LRA annotation in the same class

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3217?page=com.atlassian.jira.plugin.... ] Martin Stefanko commented on JBTM-3217: --------------------------------------- [~mmusgrov] Didn't we want to keep these LRA issues open since they are not merged to the master only to LRA branch? > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.jboss.org/browse/JBTM-3217 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Update the handling of timeout information for Compensate and Complete according to the specification. Now it's defined in the LRA annotation similarly as for the new LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-2867. ---------------------------------- Fix Version/s: 5.10.0.Final (was: 5.next) Resolution: Done > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.10.0.Final > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

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

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson closed JBTM-3195. ---------------------------------- Fix Version/s: 5.10.0.Final (was: 5.next) Resolution: Done > 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.10.0.Final > > > 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)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3193) RTS benchmarks do not run

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3193?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3193: ----------------------------------- Status: Open (was: Pull Request Sent) > RTS benchmarks do not run > ------------------------- > > Key: JBTM-3193 > URL: https://issues.jboss.org/browse/JBTM-3193 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > > There looks to be a JTA record in the object store when they are run. Could it be from a previous run? Or is it expected and if so why is the RecordManager unaware of the JTA_RECORD type for this run due to https://github.com/jbosstm/narayana/blob/1e17caa16b5efb9b16cdb2d8489a1b93... not being triggered? -- 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 November 2019