February 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3036) flight-service quickstart fails to build due to dependency failure

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3036?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3036: ---------------------------------------- [~mindcrime] if you take a later release (the last one for example 5.10.3.Final) this issue should be resolved. Would it be possible to mark this issue as fixed in a later release? > flight-service quickstart fails to build due to dependency failure > ------------------------------------------------------------------ > > Key: JBTM-3036 > URL: https://issues.redhat.com/browse/JBTM-3036 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Build System > Affects Versions: 5.8.2.Final > Reporter: Phillip Rhodes > Assignee: Michael Musgrove > Priority: Major > > [INFO] REST-AT to JTA Bridge Quickstart: JPA .............. SUCCESS [ 14.800 s] > [INFO] REST-AT to JTA Bridge Quickstart: JMS .............. SUCCESS [ 0.587 s] > [INFO] Narayana Quickstarts: REST-AT with undertow ........ SUCCESS [ 7.526 s] > [INFO] RESTTX Quickstarts ................................. SUCCESS [ 0.000 s] > [INFO] LRA Quickstart flight-service ...................... FAILURE [ 47.077 s] > [INFO] LRA Quickstart hotel-service ....................... SKIPPED > [INFO] LRA Quickstart trip-controller ..................... SKIPPED > [INFO] LRA Quickstart trip-client ......................... SKIPPED > [INFO] Run the example locally ............................ SKIPPED > [INFO] RESTTX Quickstarts ................................. SKIPPED > [INFO] xts-demo-all ....................................... SKIPPED > [INFO] xts-demo-core ...................................... SKIPPED > [INFO] xts-demo-webservices ............................... SKIPPED > [INFO] xts-demo-war ....................................... SKIPPED > [INFO] xts-demo-ear ....................................... SKIPPED > [INFO] xts-demo-test ...................................... SKIPPED > [INFO] JBoss Narayana Quickstarts: Simple WS-AT Web service, bridged to and from JTA. Bridges three servers SKIPPED > [INFO] JBoss Narayana Quickstarts: Simple WS-AT Web service, bridged to and from JTA. Bridges three servers where one service invokes another SKIPPED > [INFO] XTS Examples ....................................... SKIPPED > [INFO] XTS over SSL Quickstart ............................ SKIPPED > [INFO] setCheckedActionFactoryExample ..................... SKIPPED > [INFO] optimistic ......................................... SKIPPED > [INFO] pessimistic ........................................ SKIPPED > [INFO] stm-jta ............................................ SKIPPED > [INFO] JBoss Core Examples ................................ SKIPPED > [INFO] narayana-quickstarts-all ........................... SKIPPED > [INFO] jts-docker ......................................... SKIPPED > [INFO] Narayana Quickstarts: JBTM and OSGI ................ SKIPPED > [INFO] Narayana Quickstart: Standalone JTA 1.2 and Hibernate Quickstart SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 03:05 min > [INFO] Finished at: 2018-06-20T17:19:36Z > [INFO] Final Memory: 145M/738M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project flight-service: Could not resolve dependencies for project org.jboss.narayan a.quickstart.rts.lra:flight-service:war:5.8.2.Final: Could not find artifact org.eclipse.microprofile.lra:microprofile -lra-api:jar:1.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce... > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :flight-service -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3236) Upgrade to latest byteman release

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3236?page=com.atlassian.jira.plugin... ] Michael Musgrove resolved JBTM-3236. ------------------------------------ Resolution: Done Fixed by PR https://github.com/jbosstm/narayana/pull/1551 > Upgrade to latest byteman release > --------------------------------- > > Key: JBTM-3236 > URL: https://issues.redhat.com/browse/JBTM-3236 > Project: JBoss Transaction Manager > Issue Type: Quality Risk > Components: Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > JBTM-3226 (Byteman rule check failure with version 4.0.9) introduced a byteman version change but the new version contained a bug which has now been fixed in 4.0.10 (see BYTEMAN-391) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3231) LRA recovery test fails after restart on JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3231: ----------------------------------- Priority: Minor (was: Major) > LRA recovery test fails after restart on JDK11 > ---------------------------------------------- > > Key: JBTM-3231 > URL: https://issues.redhat.com/browse/JBTM-3231 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Minor > Fix For: 5.10.3.Final > > > CI testing: > LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/ > https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3231) LRA recovery test fails after restart on JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ] Michael Musgrove reopened JBTM-3231: ------------------------------------ Re-opened so that we can enable trace logging on CI jobs. > LRA recovery test fails after restart on JDK11 > ---------------------------------------------- > > Key: JBTM-3231 > URL: https://issues.redhat.com/browse/JBTM-3231 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.3.Final > > > CI testing: > LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/ > https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3231) LRA recovery test fails after restart on JDK11

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3231?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3231: ---------------------------------------- Note that the resolution for this issue was to run each test in its own test suite. This hypothesis is that this fix works because the root cause of the problem is that org.jboss.arquillian.container.test.api.ContainerController#kill functionality is not doing what I expect and sometimes does not release all of the container resources. Since the above resolution seems to fix the problem I do not plan to investigate any further for now. Also note that two different failure modes were observed: # org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not stop container # javax.ws.rs.ProcessingException: RESTEASY004655: Unable to invoke request: org.apache.http.NoHttpResponseException: 127.0.0.1:8080 failed to respond The plan is to enable trace logging on LRA CI jobs so that we have something to help debug the problem if it is ever seen again. > LRA recovery test fails after restart on JDK11 > ---------------------------------------------- > > Key: JBTM-3231 > URL: https://issues.redhat.com/browse/JBTM-3231 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.1.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.3.Final > > > CI testing: > LRACoordinatorTestCase=testRecovery2 fails to restart the container after crashing via byteman on JDK11. Seems to be intermittent on Amsterdam CI and more consistent on Upshift, for example: > http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/552/ > https://ci-master-jenkins-csb-narayana.cloud.paas.psi.redhat.com/job/nara... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3250) LRA caches ids of LRAs but this cache can become stale in cloud native environments

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3250?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3250: ----------------------------------- Component/s: LRA > LRA caches ids of LRAs but this cache can become stale in cloud native environments > ----------------------------------------------------------------------------------- > > Key: JBTM-3250 > URL: https://issues.redhat.com/browse/JBTM-3250 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Reporter: Michael Musgrove > Priority: Major > > The LRA implementation [caches active and recovering LRAs|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordina...]. But this cache can become stale is cloud native environments. Since an LRA is always stored in our logs from the moment of creation until successful completion a better option would be to always read the current list from the logs. This approach will facilitate use of the implementation in environments where coordinators come and go. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3220) TckContextTests.testForget failed

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3220?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3220: ---------------------------------------- [~mmusgrov] http://narayanaci1.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-LRA/9/ seems to be a different test "TckContextTests.testForgetCalledForNestedParticipantsWhenParentIsClosed:244 testForgetCalledForNestedParticipantsWhenParentIsClosed: resource should have called forget for the nested LRA expected:<1> but was:<0>" > TckContextTests.testForget failed > --------------------------------- > > Key: JBTM-3220 > URL: https://issues.redhat.com/browse/JBTM-3220 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.0.Final > > > TckContextTests.testForget:154 testForget resource status should have been called expected:<1> but was:<2> seems to fail consistently on the narayana LRA branch but it works fine on the Narayana master. I would recommend that we use this JIRA to capture any further CI LRA tck test failures. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3220) TckContextTests.testForget failed

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3220?page=com.atlassian.jira.plugin... ] Thomas Jenkinson updated JBTM-3220: ----------------------------------- Summary: TckContextTests.testForget failed (was: LRA branch failures) > TckContextTests.testForget failed > --------------------------------- > > Key: JBTM-3220 > URL: https://issues.redhat.com/browse/JBTM-3220 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.0.Final > > > TckContextTests.testForget:154 testForget resource status should have been called expected:<1> but was:<2> seems to fail consistently on the narayana LRA branch but it works fine on the Narayana master. I would recommend that we use this JIRA to capture any further CI LRA tck test failures. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3220) LRA branch failures

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/JBTM-3220?page=com.atlassian.jira.plugin... ] Thomas Jenkinson commented on JBTM-3220: ---------------------------------------- [~mmusgrov] this looks to have failed on master too: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana/571/PROFILE=LRA,j... > LRA branch failures > ------------------- > > Key: JBTM-3220 > URL: https://issues.redhat.com/browse/JBTM-3220 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Testing > Affects Versions: 5.10.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.10.0.Final > > > TckContextTests.testForget:154 testForget resource status should have been called expected:<1> but was:<2> seems to fail consistently on the narayana LRA branch but it works fine on the Narayana master. I would recommend that we use this JIRA to capture any further CI LRA tck test failures. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3250) LRA caches ids of LRAs but this cache can become stale in cloud native environments

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3250: -------------------------------------- Summary: LRA caches ids of LRAs but this cache can become stale in cloud native environments Key: JBTM-3250 URL: https://issues.redhat.com/browse/JBTM-3250 Project: JBoss Transaction Manager Issue Type: Enhancement Reporter: Michael Musgrove The LRA implementation [caches active and recovering LRAs|https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordina...]. But this cache can become stale is cloud native environments. Since an LRA is always stored in our logs from the moment of creation until successful completion a better option would be to always read the current list from the logs. This approach will facilitate use of the implementation in environments where coordinators come and go. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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 February 2020