October 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3184) LRA TckParticipantTests do not finish started LRAs

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3184?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3184: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > LRA TckParticipantTests do not finish started LRAs > -------------------------------------------------- > > Key: JBTM-3184 > URL: https://issues.jboss.org/browse/JBTM-3184 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.7.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Running TckParticipantTests leaves 4 open LRAs which will never be finished. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

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.... ] Michael Musgrove updated JBTM-3161: ----------------------------------- Fix Version/s: 5.next > 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 > Affects Versions: 5.9.8.Final > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > 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)

5 years, 2 months

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.... ] Michael Musgrove updated JBTM-3161: ----------------------------------- Affects Version/s: 5.9.8.Final > 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 > Affects Versions: 5.9.8.Final > Reporter: Matej Kralik > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > 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)

5 years, 2 months

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 commented on JBTM-3212: ---------------------------------------- I have reduced the priority since this issue should not block releasing a new narayana version > 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: Critical > 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)

5 years, 2 months

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: ----------------------------------- Priority: Critical (was: Blocker) > 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: Critical > 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)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1715) NPE when using CompensationManager within an in-flowed WS-BA transaction

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-1715?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1715: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > NPE when using CompensationManager within an in-flowed WS-BA transaction > ------------------------------------------------------------------------ > > Key: JBTM-1715 > URL: https://issues.jboss.org/browse/JBTM-1715 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Compensations > Reporter: Paul Robinson > Priority: Minor > Fix For: 5.next > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > The following error occurs if an injected CompensationManager is invoked within the scope of a compensation-based transaction that was in-flowed via a WS-BA transaction. > {quote} > 16:17:09,879 ERROR [org.jboss.as.ejb3.invocation] (default task-18) JBAS014134: EJB Invocation failed on component TestServiceService for method public void org.jboss.narayana.compensations.functiona[617/9100] > ted.TestServiceService.saveDataCancelOnFailure(java.lang.Boolean): javax.ejb.EJBException: java.lang.NullPointerException > at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:251) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:215) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT] > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:289) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [wildfly-ejb3-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPS > HOT] > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1699) Changes to the transaction SPI

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-1699?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1699: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Changes to the transaction SPI > ------------------------------ > > Key: JBTM-1699 > URL: https://issues.jboss.org/browse/JBTM-1699 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: Application Server Integration > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > Original Estimate: 1 week, 3 days > Remaining Estimate: 1 week, 3 days > > wildfly is using a number of our internal com.arjuna interfaces which we would like to resolve by providing the same functionality in the transactions SPI. > Additionally the current SPI contains a number of unused classes which need removing. > I have created https://github.com/jbosstm/jboss-transaction-spi to manage the changes. To avoid any potential confusion and to make it clear who is responsible for the SPI we will be changing the package names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-1107?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1107: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.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.13.8#713008)

5 years, 2 months

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Michael Musgrove updated JBTM-741: ---------------------------------- Fix Version/s: 5.next (was: 5.10.0.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.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1719) Improve test coverage for REST-AT multiplexor.

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-1719?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-1719: ----------------------------------- Fix Version/s: 5.next (was: 5.10.0.Final) > Improve test coverage for REST-AT multiplexor. > ---------------------------------------------- > > Key: JBTM-1719 > URL: https://issues.jboss.org/browse/JBTM-1719 > Project: JBoss Transaction Manager > Issue Type: Task > Components: REST > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.next > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Implement more unit and integration tests to cover more aspects of multiplexor functionality (https://github.com/jbosstm/narayana/tree/master/rts/at/integration). Especially recovery. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 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 October 2019