July 2020 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3335) Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat)

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3335?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3335: ----------------------------------- Git Pull Request: https://github.com/jbosstm/quickstart/pull/291 > Upgrade jca + tomcat quickstart (org.jboss.narayana.quickstarts:jca-and-tomcat) > ------------------------------------------------------------------------------- > > Key: JBTM-3335 > URL: https://issues.redhat.com/browse/JBTM-3335 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Quickstarts > Reporter: Michael Musgrove > Assignee: Mayank Kunwar > Priority: Blocker > > The jca + tomcat quickstart is using a very old version of hibernate-validator (org.hibernate:hibernate-validator:5.0.1.Final) and needs updating to use a more recent release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3348) Add some progress logging to the performance benchmark script

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3348?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3348: -------------------------------------- Assignee: (was: Michael Musgrove) > Add some progress logging to the performance benchmark script > ------------------------------------------------------------- > > Key: JBTM-3348 > URL: https://issues.redhat.com/browse/JBTM-3348 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI, Performance Testing > Affects Versions: 5.10.5.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The [performance benchmark script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip... seen to time out on a recent [pull request|https://github.com/jbosstm/performance/pull/78] with no indication of why the job was not making progress. > Whenever the [benchmark run script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] starts a new run it should report which test iteration it is running, then we will at least be able to tell how much progress was made before Jenkins times out the build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3348) Add some progress logging to the performance benchmark script

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3348?page=com.atlassian.jira.plugin... ] Michael Musgrove updated JBTM-3348: ----------------------------------- Description: The [performance benchmark script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip... seen to time out on a recent [pull request|https://github.com/jbosstm/performance/pull/78] with no indication of why the job was not making progress. Whenever the [benchmark run script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] starts a new run it should report which test iteration it is running, then we will at least be able to tell how much progress was made before Jenkins times out the build. was: The [peformance benchmark script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] was seen to time out on a recent [pull request|https://github.com/jbosstm/performance/pull/78] with no indication of why the job was not making progress. [https://github.com/jbosstm/performance/blob/master/narayana/scripts/hudso...] Whenever the [benchmark run script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] starts a new run it should report which test iteration it is running, then we will at least be able to tell how much progress was made before jenkins times out the build. > Add some progress logging to the performance benchmark script > ------------------------------------------------------------- > > Key: JBTM-3348 > URL: https://issues.redhat.com/browse/JBTM-3348 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: CI, Performance Testing > Affects Versions: 5.10.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The [performance benchmark script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip... seen to time out on a recent [pull request|https://github.com/jbosstm/performance/pull/78] with no indication of why the job was not making progress. > Whenever the [benchmark run script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] starts a new run it should report which test iteration it is running, then we will at least be able to tell how much progress was made before Jenkins times out the build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3348) Add some progress logging to the performance benchmark script

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3348: -------------------------------------- Summary: Add some progress logging to the performance benchmark script Key: JBTM-3348 URL: https://issues.redhat.com/browse/JBTM-3348 Project: JBoss Transaction Manager Issue Type: Enhancement Components: CI, Performance Testing Affects Versions: 5.10.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The [peformance benchmark script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] was seen to time out on a recent [pull request|https://github.com/jbosstm/performance/pull/78] with no indication of why the job was not making progress. [https://github.com/jbosstm/performance/blob/master/narayana/scripts/hudso...] Whenever the [benchmark run script|[https://github.com/jbosstm/performance/blob/master/narayana/scrip...] starts a new run it should report which test iteration it is running, then we will at least be able to tell how much progress was made before jenkins times out the build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3347) CI performance job fails because it uses the wrong authorization credentials

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3347?page=com.atlassian.jira.plugin... ] Michael Musgrove closed JBTM-3347. ---------------------------------- Resolution: Rejected This issue report was not the reason for the build failure. It looks like the script narayana/scripts/hudson/bm.sh may have hung and needs more investigation. Therefore I am rejecting the issue. > CI performance job fails because it uses the wrong authorization credentials > ---------------------------------------------------------------------------- > > Key: JBTM-3347 > URL: https://issues.redhat.com/browse/JBTM-3347 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: CI, Performance Testing > Affects Versions: 5.10.5.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The performance job is failing because it is using the wrong authorization credentials: > ./scripts/hudson/jenkins.sh: line 110: 17647 Terminated ./narayana/scripts/hudson/bm.sh > '[' 143 = 0 ']' > fatal 'BM properties failed' > comment_on_pull 'Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed' > '[' 1 = '' ']' > echo origin/pull/78/head > awk -F pull '\{ print $2 }' > awk -F / '\{ print $2 }' > PULL_NUMBER=78 > '[' 78 '!=' '' ']' > JSON='\{ "body": "Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed" }' > curl -d '\{ "body": "Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed" }' -H 'Authorization: token ****' https://api.github.com/repos/jbosstm/performance/issues/78/comments -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3347) CI performance job fails because it uses the wrong authorization credentials

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3347: -------------------------------------- Summary: CI performance job fails because it uses the wrong authorization credentials Key: JBTM-3347 URL: https://issues.redhat.com/browse/JBTM-3347 Project: JBoss Transaction Manager Issue Type: Bug Components: CI, Performance Testing Affects Versions: 5.10.5.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The performance job is failing because it is using the wrong authorization credentials: ./scripts/hudson/jenkins.sh: line 110: 17647 Terminated ./narayana/scripts/hudson/bm.sh '[' 143 = 0 ']' fatal 'BM properties failed' comment_on_pull 'Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed' '[' 1 = '' ']' echo origin/pull/78/head awk -F pull '\{ print $2 }' awk -F / '\{ print $2 }' PULL_NUMBER=78 '[' 78 '!=' '' ']' JSON='\{ "body": "Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed" }' curl -d '\{ "body": "Tests failed (http://narayanaci1.eng.hst.ams2.redhat.com/job/btny-pulls-performance/36/): BM properties failed" }' -H 'Authorization: token ****' https://api.github.com/repos/jbosstm/performance/issues/78/comments -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3307) LRACoordinatorRecovery2TestCase regularly fails on CI

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3307?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3307: ----------------------------------- Status: Open (was: Pull Request Sent) The PR disabled the test but did not fix the issue. I'm setting to reject as currently there is no PR available to fix this issue. (I started to investigate on this but I assume there should be done refactoring of tests first to get this running on Quarkus as well to see how that behaves there too.) > LRACoordinatorRecovery2TestCase regularly fails on CI > ----------------------------------------------------- > > Key: JBTM-3307 > URL: https://issues.redhat.com/browse/JBTM-3307 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.10.4.Final > Reporter: Michael Musgrove > Assignee: Ondrej Chaloupka > Priority: Blocker > Fix For: 5.next > > > The test regularly fails CI > [ERROR] testRecovery2(io.narayana.lra.coordinator.LRACoordinatorRecovery2TestCase) Time elapsed: 30.455 s <<< FAILURE! > java.lang.AssertionError: LRA with short timeout should not be active > presumably due to a timing issue (since I cannot reproduce it on my laptop). I will see if there is a way to make the test more robust. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3346) Journal store file count grows unbounded

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/JBTM-3346?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated JBTM-3346: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 5.next Resolution: Done > Journal store file count grows unbounded > ---------------------------------------- > > Key: JBTM-3346 > URL: https://issues.redhat.com/browse/JBTM-3346 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transaction Core > Affects Versions: 5.10.5.Final > Reporter: Jonathan Halliday > Assignee: Jonathan Halliday > Priority: Minor > Fix For: 5.next > > > Under sustained high load the HornetQ (Artemis) Journal store creates new store files instead of recycling old ones. Whilst bounding write latency this will, over a prolonged interval on sufficiently fast storage media, lead to excessive use of storage space. For our use case it's preferable to have the journal generate write-throttling backpressure from the file recycler. ref https://issues.apache.org/jira/browse/ARTEMIS-2837 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3245) Check the behaviour when LRA enlistment fails due to coordinator unavailability

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3245?page=com.atlassian.jira.plugin... ] Michael Musgrove commented on JBTM-3245: ---------------------------------------- There is no TCK test for this scenario because the TCK does not assume any particular implementation technique. Narayana supports remote coordinators so it would be useful to have a test for this. Code inspection shows that we do do the correct thing: the code that tries to enlist a participant (ServerLRAFilter) catches WebApplicationException and aborts the JAX-RS request. The after filter then checks the JAX-RS response code and cancels the LRA if the code is present in the "cancelOn..." LRA attribute element. But we do need to test it although whether the blocker priority is correct is debatable. > Check the behaviour when LRA enlistment fails due to coordinator unavailability > ------------------------------------------------------------------------------- > > Key: JBTM-3245 > URL: https://issues.redhat.com/browse/JBTM-3245 > Project: JBoss Transaction Manager > Issue Type: Task > Components: LRA > Affects Versions: 5.10.3.Final > Reporter: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > There is no test that verifies an LRA is cancelled if a participant tries to join with an LRA and fails because an external coordinator is unavailable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3340) LRA CDI Participant quickstart failure

by Michael Musgrove (Jira)

[ https://issues.redhat.com/browse/JBTM-3340?page=com.atlassian.jira.plugin... ] Michael Musgrove reassigned JBTM-3340: -------------------------------------- Assignee: (was: Michael Musgrove) > LRA CDI Participant quickstart failure > -------------------------------------- > > Key: JBTM-3340 > URL: https://issues.redhat.com/browse/JBTM-3340 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA, Quickstarts > Affects Versions: 5.10.5.Final > Reporter: Michael Musgrove > Priority: Major > Fix For: 5.next > > > The quickstart in directory rts/lraexamples/cdi-participant failed on IPv6 because the target server (hosting an LRA participant) could not be halted (kill -0 reported the process as still alive): > [http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts-ipv6/28/] > [0m+ kill -0 23244 > + '[' 0 '!=' 1 ']' > + echo 'cdi service on pid 23244 failed to halt' > + res=1 > cdi service on pid 23244 failed to halt -- This message was sent by Atlassian Jira (v7.13.8#713008)

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