April 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3261) Merge LRA branch to the master branch

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3261?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3261: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1584 > Merge LRA branch to the master branch > ------------------------------------- > > Key: JBTM-3261 > URL: https://issues.redhat.com/browse/JBTM-3261 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Reporter: Michael Musgrove > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > We have a git branch called [LRA|https://github.com/jbosstm/narayana/tree/LRA] which tracks the [microprofile-lra|https://github.com/eclipse/microprofile-lra] project. > This branch should periodically by synced up with the master branch. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3272: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done I just hit this issue which has been already resolved thus I'm setting the right jira status. > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3262) was added while fixing https://issues.redhat.com/browse/JBTM-3262 in order to verify that records written with the old string serialization code could be read by later revisions of that code. Since the same string serialization code is used for all store types we only need to test against a single store type (adding the same test for all store types would be overkill). > The test is coded to work with stores that inherit from ObjectStore (such as ShadowNoFileLockStore) but it fails with some store types such as the JDBCStore with the error: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3265) Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3265?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3265: ----------------------------------- Git Pull Request: https://github.com/jbosstm/narayana/pull/1567 > Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA > -------------------------------------------------------------- > > Key: JBTM-3265 > URL: https://issues.redhat.com/browse/JBTM-3265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > FailingParticipantCallsIT.testFailingAfterLRA fails regularly on CI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3265) Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3265?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3265: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Failing LRA test FailingParticipantCallsIT#testFailingAfterLRA > -------------------------------------------------------------- > > Key: JBTM-3265 > URL: https://issues.redhat.com/browse/JBTM-3265 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > FailingParticipantCallsIT.testFailingAfterLRA fails regularly on CI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3272) The test for reading old records should only run against filesystem stores

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3272?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka reassigned JBTM-3272: -------------------------------------- Assignee: Michael Musgrove > The test for reading old records should only run against filesystem stores > -------------------------------------------------------------------------- > > Key: JBTM-3272 > URL: https://issues.redhat.com/browse/JBTM-3272 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The test (com.hp.mwtests.ts.arjuna.objectstore.TestJBTM3262) was added while fixing https://issues.redhat.com/browse/JBTM-3262 in order to verify that records written with the old string serialization code could be read by later revisions of that code. Since the same string serialization code is used for all store types we only need to test against a single store type (adding the same test for all store types would be overkill). > The test is coded to work with stores that inherit from ObjectStore (such as ShadowNoFileLockStore) but it fails with some store types such as the JDBCStore with the error: > bq. TestJBTM3249.test:86 com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore cannot be cast to com.arjuna.ats.arjuna.objectstore.ObjectStore -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3279) TCK test TckRecoveryTests fails with configuration error

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3279?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka closed JBTM-3279. ---------------------------------- Resolution: Duplicate Issue I assume this was fixed by the PR for https://issues.redhat.com/browse/JBTM-3283. Feel free to reopen if I'm wrong. > TCK test TckRecoveryTests fails with configuration error > -------------------------------------------------------- > > Key: JBTM-3279 > URL: https://issues.redhat.com/browse/JBTM-3279 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > Running TckRecoveryTests on my machine gives the following error: > {noformat} > [INFO] Running org.eclipse.microprofile.lra.tck.TckRecoveryTests > [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.735 s <<< FAILURE! - in org.eclipse.microprofile.lra.tck.TckRecoveryTests > [ERROR] org.eclipse.microprofile.lra.tck.TckRecoveryTests Time elapsed: 0.734 s <<< ERROR! > java.lang.RuntimeException: Could not create statement > Caused by: java.lang.RuntimeException: Could not lookup value for field private java.net.URL org.eclipse.microprofile.lra.tck.TckRecoveryTests.deploymentURL > Caused by: java.lang.IllegalArgumentException: Cannot parse java VM arguments -Dthorntail.http.host=localhost -Dthorntail.http.port=8180 -Dlra.tck.coordinator.hostname=localhost -Dlra.tck.coordinator.port=8080 -Dlra.http.host=localhost -Dlra.http.port=8080 -Dlra.tck.consistency.shortDelay=1000 -Dlra.tck.consistency.longDelay=20000 > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3278) Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272)

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3278?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3278: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Require that LRA method must be combined with Compensate or AfterLRA (LRA issue 272) > ------------------------------------------------------------------------------------ > > Key: JBTM-3278 > URL: https://issues.redhat.com/browse/JBTM-3278 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > LRA issue 272 - https://github.com/eclipse/microprofile-lra/issues/272 > We must require (fail the deployment otherwise) that LRA method must be combined with either Compensate method or AfterLRA method in the same LRA resource. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3281) Forget should be called for nested participant when the parent LRA is closed

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3281?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3281: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Forget should be called for nested participant when the parent LRA is closed > ---------------------------------------------------------------------------- > > Key: JBTM-3281 > URL: https://issues.redhat.com/browse/JBTM-3281 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > Fix For: 5.next > > > The TCK test {{TckContextTests.testForgetCalledForNestedParticipantsWhenParentIsClosed}} is currently failing. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3287) ThornTail LRA coordinator cannot start

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3287?page=com.atlassian.jira.plugin... ] Issue was automatically transitioned when Michael Musgrove created pull request #1597 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > ThornTail LRA coordinator cannot start > -------------------------------------- > > Key: JBTM-3287 > URL: https://issues.redhat.com/browse/JBTM-3287 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > {noformat} > Caused by: java.lang.NoClassDefFoundError: org/eclipse/microprofile/lra/annotation/LRAStatus > {noformat} > It seems that the LRA API dependency needs to be defined directly in the lra-coordinator-thorntail module. It isn't picked up from transitive dependency (lra-coordinator-jar). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3287) ThornTail LRA coordinator cannot start

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3287: ------------------------------------- Summary: ThornTail LRA coordinator cannot start Key: JBTM-3287 URL: https://issues.redhat.com/browse/JBTM-3287 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.4.Final Reporter: Martin Stefanko Assignee: Martin Stefanko {noformat} Caused by: java.lang.NoClassDefFoundError: org/eclipse/microprofile/lra/annotation/LRAStatus {noformat} It seems that the LRA API dependency needs to be defined directly in the lra-coordinator-thorntail module. It isn't picked up from transitive dependency (lra-coordinator-jar). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 April 2020