December 2018 - jbossts-issues - Jboss List Archives

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

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3046: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.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.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3042) API to get detailed LRA information should not include stats type data

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3042?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3042: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > API to get detailed LRA information should not include stats type data > ---------------------------------------------------------------------- > > Key: JBTM-3042 > URL: https://issues.jboss.org/browse/JBTM-3042 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The interface to obtain information about an LRA [1] includes data such as when the LRA was started and ended. This type of information is more appropriate to monitoring and statistics gathering rather than core LRA info. Not all implementations may want to / be able to report these accurately so perhaps move them to an extended optional interface > [1] https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-client/src/ma... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3086) dependentLRA test failure

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3086: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/...] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/sr...] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3073) Do not mandate JAX-RS annotations on @Compensate/@Complete methods

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3073?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3073: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Do not mandate JAX-RS annotations on @Compensate/@Complete methods > ------------------------------------------------------------------ > > Key: JBTM-3073 > URL: https://issues.jboss.org/browse/JBTM-3073 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: LRA > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Cloned from [https://github.com/eclipse/microprofile-lra/issues/35|http://example.com]: > It is up to the implementation on how the Compensate methods are called. > This could be through JAX-RS calls but this should not be the only way (although an implementation will probably only implement one method). This makes it easier to use the 'events' way of coordination. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3072) Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3072?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3072: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Add a test to verify the behaviour of LRA.Type.REQUIRES_NEW combined with LRA.delayClose > ---------------------------------------------------------------------------------------- > > Key: JBTM-3072 > URL: https://issues.jboss.org/browse/JBTM-3072 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA, Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a test that verifies the correct behaviour when a method is annotated with both REQUIRES_NEW and delayClose, ie something like: > {code} > @PUT > @Path(ActivityController.ACCEPT_WORK) > @LRA(value = LRA.Type.REQUIRES_NEW, delayClose = true) > public Response doInNewLRA( ....) {...} > {code} > The expected behaviour is: > {code} > /** > * If called outside a LRA context a new LRA will be created for the > * the duration of the method call and when the call completes it will > * be closed (this behaviour can be overridden using the > * {@link LRA#delayClose} attribute). > * > * If called inside a LRA context it will be suspended and a new LRA > * context will be created for the duration of the call. When the method > * finishes this new LRA will be closed and the original context will be > * resumed. This behaviour can be overridden using the > * {@link LRA#delayClose} attribute) in which case the original LRA > * remains suspended and the new LRA becomes the active one and only > * when that one is terminated will the original context be resumed. > */ > REQUIRES_NEW, > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3079) InboundBridge recovery aborts live transactions

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3079?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka closed JBTM-3079. --------------------------------- > InboundBridge recovery aborts live transactions > ----------------------------------------------- > > Key: JBTM-3079 > URL: https://issues.jboss.org/browse/JBTM-3079 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: TxBridge > Affects Versions: 5.5.32.Final, 5.9.0.Final > Environment: EAP 7.1.5 / 5.5.32.Final > Reporter: Jonathan Halliday > Assignee: Tom Jenkinson > Priority: Critical > Fix For: 5.5.34.Final, 5.9.2.Final > > Attachments: jbtm3079.patch > > > During a recovery pass, the InboundBridgeRecoveryManager scans for subordinate XA branches that may need cleanup. The filtering process applied by checkXid correctly excludes tx that are not owned by the bridge, but fails to ignore those that are owned but also still live. Therefore, a race condition exists such that the recovery process may incorrectly abort a branch if invoked between the prepare and commit steps, resulting in data corruption relative to other committed branches from the parent i.e. Heuristic outcomes. > TRACE [org.jboss.jbossts.txbridge] (TaskWorker-3) BridgeDurableParticipant.prepare(Xid=< 131080, 35, 64, ... >) > TRACE [org.jboss.jbossts.txbridge] (Periodic Recovery) rolling back orphaned subordinate tx < 131080, 35, 64, ... > > ERROR [org.jboss.jbossts.txbridge] (TaskWorker-8) ARJUNA033004: commit on Xid=< 131080, 35, 64, ... > failed: javax.transaction.xa.XAException > It is necessary to enhance checkXid to validate against known live tx. The easiest way would seem to be to have the InboundBridgeManager singleton hold a lookup table of live tx, effectively a secondary index into its existing collection of InboundBridges, against which the recovery system can validate the in-doubt Xid. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Ondra Chaloupka (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka updated JBTM-3087: ---------------------------------- Fix Version/s: 5.next (was: 5.9.2.Final) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3087?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1395 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Ensure the LRA implementation is up to date > ------------------------------------------- > > Key: JBTM-3087 > URL: https://issues.jboss.org/browse/JBTM-3087 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3087) Ensure the LRA implementation is up to date

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3087: -------------------------------------- Summary: Ensure the LRA implementation is up to date Key: JBTM-3087 URL: https://issues.jboss.org/browse/JBTM-3087 Project: JBoss Transaction Manager Issue Type: Task Components: LRA Affects Versions: 5.9.1.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The microprofile-lra API has undergone a number of changes recently. The narayana implementation of the specification needs updating to match the new version of it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3086) dependentLRA test failure

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3086?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3086: ---------------------------------------- The test is invokes a method annotated with LRA NOT_SUPPORTED and the method then starts an LRA via the API. This LRA should be available to the caller when the annotated method completes. However [microprofile lra issue 40|https://github.com/eclipse/microprofile-lra/issues/40] changed the default behaviour of the `terminal` attribute of an LRA which uncovered this bug since now the LRA started via the client API is incorrectly closed by the implementation (see the ServerLRAFilter JAX-RS filter). > dependentLRA test failure > ------------------------- > > Key: JBTM-3086 > URL: https://issues.jboss.org/browse/JBTM-3086 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The TCK test [dependentLRA|https://github.com/eclipse/microprofile-lra/blob/master/tck/...] in the microprofile-lra test suite fails if the [terminal attribute of the LRA annotation|https://github.com/eclipse/microprofile-lra/blob/master/api/sr...] is set to true. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 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 December 2018