April 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3229) Allow to enlist AfterLRA listeners after the LRA enters the ending phase

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3229?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3229: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Allow to enlist AfterLRA listeners after the LRA enters the ending phase > ------------------------------------------------------------------------ > > Key: JBTM-3229 > URL: https://issues.redhat.com/browse/JBTM-3229 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.1.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > > https://github.com/eclipse/microprofile-lra/issues/241 > The specification was updated to allow AfterLRA listeners (LRA resources without Compensate method but with the AfterLRA method) to enlist for AfterLRA notification even after the LRA enters the ending (closing/canceling) phase. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

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

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3217?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3217: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Take Compensate and Complete timeout information from the LRA annotation in the same class > ------------------------------------------------------------------------------------------ > > Key: JBTM-3217 > URL: https://issues.redhat.com/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: Blocker > Fix For: 5.next > > > 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

1
0
0 / 0

[JBoss JIRA] (JBTM-3204) Upgrade LRA TCK recovery handling to accommodate specification changes

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3204?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3204: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade LRA TCK recovery handling to accommodate specification changes > ----------------------------------------------------------------------- > > Key: JBTM-3204 > URL: https://issues.redhat.com/browse/JBTM-3204 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > Fix For: 5.next > > > LRA TCK added a new way of handling LRA recovery in https://github.com/eclipse/microprofile-lra/commit/52b799768b3d0fa1746f2b.... Update the implementation to accommodate these changes. > Also update the LRA versions to the latest snapshots: > <version.microprofile.lra.api>1.0-20190927.061209-550</version.microprofile.lra.api> > <version.microprofile.lra.tck>1.0-20190927.061211-550</version.microprofile.lra.tck> > diff: [https://github.com/eclipse/microprofile-lra/compare/1.0-RC1...fab960eede3...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3221) Refactor NarayanaLRARecovery according to the specification upgrades

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3221?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3221: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Refactor NarayanaLRARecovery according to the specification upgrades > -------------------------------------------------------------------- > > Key: JBTM-3221 > URL: https://issues.redhat.com/browse/JBTM-3221 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > > Refactor the NarayanaLRARecovery according to the spec changes in [LRA issue 249|https://github.com/eclipse/microprofile-lra/issues/249]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3221) Refactor NarayanaLRARecovery according to the specification upgrades

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3221?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3221: ----------------------------------- Fix Version/s: 5.next > Refactor NarayanaLRARecovery according to the specification upgrades > -------------------------------------------------------------------- > > Key: JBTM-3221 > URL: https://issues.redhat.com/browse/JBTM-3221 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.0.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Blocker > Fix For: 5.next > > > Refactor the NarayanaLRARecovery according to the spec changes in [LRA issue 249|https://github.com/eclipse/microprofile-lra/issues/249]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3271) javadoc error when building with JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3271?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3271: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > javadoc error when building with JDK11 > -------------------------------------- > > Key: JBTM-3271 > URL: https://issues.redhat.com/browse/JBTM-3271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: > bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > More context is here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8212233 > A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3271) javadoc error when building with JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3271?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3271: -------------------------------------- Assignee: Ondrej Chaloupka > javadoc error when building with JDK11 > -------------------------------------- > > Key: JBTM-3271 > URL: https://issues.redhat.com/browse/JBTM-3271 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Assignee: Ondrej Chaloupka > Priority: Major > Fix For: 5.next > > > When we build using JDK11 we get javadoc errors. For example building ArjunaCore/arjunacore: > bq. javadoc: error - The code being documented uses modules but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module. > More context is here: https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8212233 > A fix is to configure the javadoc plugin (org.apache.maven.plugins:maven-javadoc-plugin) to use <source>8</source> in the plugin configuration section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3280) TckTests$timelimit is failing on CI

by Martin Stefanko (Jira)

Martin Stefanko created JBTM-3280: ------------------------------------- Summary: TckTests$timelimit is failing on CI Key: JBTM-3280 URL: https://issues.redhat.com/browse/JBTM-3280 Project: JBoss Transaction Manager Issue Type: Bug Components: LRA Affects Versions: 5.10.3.Final Reporter: Martin Stefanko Assignee: Martin Stefanko Not reproducible locally so far. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (JBTM-3277) LRA quickstarts fail on Narayana AMS CI with curl could not find the target server

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3277?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3277: ----------------------------------- Description: The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. The workaround the setup the curl should force the IPv4 to be used {{-4}}. The CI error is observed with errors {code} ===== injecting a fault which should halt the service on pid ... WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 ... Failed to connect to ::1: Network is unreachable {code} The same happens on tomcat driver example where error is like {code} % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to ::1: Network is unreachable Listening for transport dt_socket at address: 8000 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/9.0.7 {code} was: The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. The workaround the setup the curl should force the IPv4 to be used {{-4}}. The CI error is observed with errors {code} ===== injecting a fault which should halt the service on pid ... WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 ... Failed to connect to ::1: Network is unreachable {code} > LRA quickstarts fail on Narayana AMS CI with curl could not find the target server > ---------------------------------------------------------------------------------- > > Key: JBTM-3277 > URL: https://issues.redhat.com/browse/JBTM-3277 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Minor > > The quickstarts fails on CI as it seems the CI is now dual stack and for normal run we need to enforce the IPv4 to be used. > The when {{localhost}} is used then {{curl}} is directed to {{::1}} while java Thorntail is started at {{0.0.0.0}}. > The workaround the setup the curl should force the IPv4 to be used {{-4}}. > The CI error is observed with errors > {code} > ===== injecting a fault which should halt the service on pid > ... > WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8080 > ... > Failed to connect to ::1: Network is unreachable > {code} > The same happens on tomcat driver example where error is like > {code} > % Total % Received % Xferd Average Speed Time Time Time Current > Dload Upload Total Spent Left Speed > 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed to connect to ::1: Network is unreachable > Listening for transport dt_socket at address: 8000 > INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version: Apache Tomcat/9.0.7 > {code} -- 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 Martin Stefanko (Jira)

Martin Stefanko created JBTM-3279: ------------------------------------- Summary: 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 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues April 2020