October 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3195) CacheStore failed a read_committed check in CI

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson edited comment on JBTM-3195 at 10/16/19 3:44 AM: ------------------------------------------------------------------ The key element could be related to: {code} "AsyncStoreThread" #21 daemon prio=5 os_prio=0 tid=0x00007fb16c9a6000 nid=0x19a1 runnable [0x00007fb0cca37000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:783) - locked <0x000000059236c830> (a java.util.NoSuchElementException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.util.NoSuchElementException.<init>(NoSuchElementException.java:46) at java.util.LinkedList.removeLast(LinkedList.java:283) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.doWork(CacheStore.java:670) - locked <0x0000000080232220> (a java.util.LinkedList) - locked <0x0000000080232010> (a [Ljava.util.LinkedList;) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.run(CacheStore.java:606) - locked <0x00000000802322e0> (a java.lang.Object) {code} I saw this as appearing in a loop during local testing. was (Author: tomjenkinson): The key element is from: {code} "AsyncStoreThread" #21 daemon prio=5 os_prio=0 tid=0x00007fb16c9a6000 nid=0x19a1 runnable [0x00007fb0cca37000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:783) - locked <0x000000059236c830> (a java.util.NoSuchElementException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.util.NoSuchElementException.<init>(NoSuchElementException.java:46) at java.util.LinkedList.removeLast(LinkedList.java:283) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.doWork(CacheStore.java:670) - locked <0x0000000080232220> (a java.util.LinkedList) - locked <0x0000000080232010> (a [Ljava.util.LinkedList;) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.run(CacheStore.java:606) - locked <0x00000000802322e0> (a java.lang.Object) {code} I saw this as appearing in a loop during local testing. > CacheStore failed a read_committed check in CI > ---------------------------------------------- > > Key: JBTM-3195 > URL: https://issues.jboss.org/browse/JBTM-3195 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > The test hung because of an assertion failing before the threads were all joined: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/tests/c... > No state found while trying to read 0:ffffac110012:863a:5d7bfbf4:11 > Thread for 0:ffffac110012:863a:5d7bfbf4:11 failed > Was in the output (no other errors) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3195) CacheStore failed a read_committed check in CI

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3195: ----------------------------------- Fix Version/s: 5.next > CacheStore failed a read_committed check in CI > ---------------------------------------------- > > Key: JBTM-3195 > URL: https://issues.jboss.org/browse/JBTM-3195 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > The test hung because of an assertion failing before the threads were all joined: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/tests/c... > No state found while trying to read 0:ffffac110012:863a:5d7bfbf4:11 > Thread for 0:ffffac110012:863a:5d7bfbf4:11 failed > Was in the output (no other errors) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2867) Investigate un-_workList protected access to _work object

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-2867?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-2867: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1518 > Investigate un-_workList protected access to _work object > --------------------------------------------------------- > > Key: JBTM-2867 > URL: https://issues.jboss.org/browse/JBTM-2867 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > During investigation of JBTM-2865 it was detected that the _work object can be accessed outside of the _workList synchronized block. Notably this seems to be a .remove() operation on it which can mutate the struct and may cause issues. > For example, this looks wrong: > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... > If > https://github.com/tomjenkinson/narayana/blob/adda493b7bbd030eb405e3ef209... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3195) CacheStore failed a read_committed check in CI

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson reassigned JBTM-3195: -------------------------------------- Assignee: Thomas Jenkinson (was: Michael Musgrove) > CacheStore failed a read_committed check in CI > ---------------------------------------------- > > Key: JBTM-3195 > URL: https://issues.jboss.org/browse/JBTM-3195 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > > The test hung because of an assertion failing before the threads were all joined: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/tests/c... > No state found while trying to read 0:ffffac110012:863a:5d7bfbf4:11 > Thread for 0:ffffac110012:863a:5d7bfbf4:11 failed > Was in the output (no other errors) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3195) CacheStore failed a read_committed check in CI

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3195?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson commented on JBTM-3195: ---------------------------------------- The key element is from: {code} "AsyncStoreThread" #21 daemon prio=5 os_prio=0 tid=0x00007fb16c9a6000 nid=0x19a1 runnable [0x00007fb0cca37000] java.lang.Thread.State: RUNNABLE at java.lang.Throwable.fillInStackTrace(Native Method) at java.lang.Throwable.fillInStackTrace(Throwable.java:783) - locked <0x000000059236c830> (a java.util.NoSuchElementException) at java.lang.Throwable.<init>(Throwable.java:250) at java.lang.Exception.<init>(Exception.java:54) at java.lang.RuntimeException.<init>(RuntimeException.java:51) at java.util.NoSuchElementException.<init>(NoSuchElementException.java:46) at java.util.LinkedList.removeLast(LinkedList.java:283) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.doWork(CacheStore.java:670) - locked <0x0000000080232220> (a java.util.LinkedList) - locked <0x0000000080232010> (a [Ljava.util.LinkedList;) at com.arjuna.ats.internal.arjuna.objectstore.AsyncStore.run(CacheStore.java:606) - locked <0x00000000802322e0> (a java.lang.Object) {code} I saw this as appearing in a loop during local testing. > CacheStore failed a read_committed check in CI > ---------------------------------------------- > > Key: JBTM-3195 > URL: https://issues.jboss.org/browse/JBTM-3195 > Project: JBoss Transaction Manager > Issue Type: Bug > Reporter: Thomas Jenkinson > Assignee: Michael Musgrove > Priority: Major > > The test hung because of an assertion failing before the threads were all joined: https://github.com/jbosstm/narayana/blob/master/ArjunaCore/arjuna/tests/c... > No state found while trying to read 0:ffffac110012:863a:5d7bfbf4:11 > Thread for 0:ffffac110012:863a:5d7bfbf4:11 failed > Was in the output (no other errors) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3211) Re-enable lra-test-basic

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3211?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3211: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Re-enable lra-test-basic > ------------------------ > > Key: JBTM-3211 > URL: https://issues.jboss.org/browse/JBTM-3211 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > This [particular test|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-test/lra...] is for the Narayana specific LRA client which was temporarily disabled during PR 1515. It needs to be re-enabled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3211) Re-enable lra-test-basic

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3211?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3211: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jbosstm/narayana/pull/1515 > Re-enable lra-test-basic > ------------------------ > > Key: JBTM-3211 > URL: https://issues.jboss.org/browse/JBTM-3211 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > This [particular test|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-test/lra...] is for the Narayana specific LRA client which was temporarily disabled during PR 1515. It needs to be re-enabled. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3189) Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3189?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3189: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA > ------------------------------------------------------------------------------------------- > > Key: JBTM-3189 > URL: https://issues.jboss.org/browse/JBTM-3189 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When an LRA is cancelled from a timer the cancellation is performed by a thread from the ForkJoinPool. None of the Resteasy JAX-RS providers are available on this thread. Outgoing JAX-RS calls made from this thread will then fail. > Since the LRA coordinator only uses REST calls it would be better to use something like java.net.HttpURLConnection or wait for java.net.http.HttpClient which is in JDK 11. > But as an interim fix I would suggest that the timeout handler sets the status to Cancelling and then when the LRA is later closed we check whether the timer triggered and cancel the LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3189) Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3189?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3189: ---------------------------------------- Another interim option is to use Apache HttpClient > Resteasy providers are absent when a thread from the ForkJoinPool is used to cancel the LRA > ------------------------------------------------------------------------------------------- > > Key: JBTM-3189 > URL: https://issues.jboss.org/browse/JBTM-3189 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > When an LRA is cancelled from a timer the cancellation is performed by a thread from the ForkJoinPool. None of the Resteasy JAX-RS providers are available on this thread. Outgoing JAX-RS calls made from this thread will then fail. > Since the LRA coordinator only uses REST calls it would be better to use something like java.net.HttpURLConnection or wait for java.net.http.HttpClient which is in JDK 11. > But as an interim fix I would suggest that the timeout handler sets the status to Cancelling and then when the LRA is later closed we check whether the timer triggered and cancel the LRA. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3212) Ensure that an LRA timeout timer is restarted after a crash

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3212?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3212: ----------------------------------- Priority: Blocker (was: Major) > Ensure that an LRA timeout timer is restarted after a crash > ----------------------------------------------------------- > > Key: JBTM-3212 > URL: https://issues.jboss.org/browse/JBTM-3212 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Blocker > Fix For: 5.next > > > LRAs can be timed out. After a crash the time should be restarted. Currently this functionality is marked as a TODO item: > > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... > and > https://github.com/jbosstm/narayana/blob/master/rts/lra/lra-coordinator-j... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 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 October 2019