September 2019 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3198) LRA Quickstart failures

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3198: -------------------------------------- Summary: LRA Quickstart failures Key: JBTM-3198 URL: https://issues.jboss.org/browse/JBTM-3198 Project: JBoss Transaction Manager Issue Type: Bug Components: Demonstrator, LRA, Quickstarts Affects Versions: 5.9.8.Final, 5.9.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The lra coordinator jar name in the narayana full distribution has been renamed. Some of the LRA quickstarts need to reflect this name change. See for example the following CI job: http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/380/c... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3197) Include an STM quickstart running on Quarkus (including native mode)

by Michael Musgrove (Jira)

[ https://issues.jboss.org/browse/JBTM-3197?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3197: ----------------------------------- Component/s: STM (was: LRA) > Include an STM quickstart running on Quarkus (including native mode) > -------------------------------------------------------------------- > > Key: JBTM-3197 > URL: https://issues.jboss.org/browse/JBTM-3197 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Demonstrator, Quickstarts, STM > Affects Versions: 5.9.8.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Major > Fix For: 5.next > > > Add a quickstart that shows how to create an STM example running on Quarkus. The quickstart should also include instructions for building a native executable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3197) Include an STM quickstart running on Quarkus (including native mode)

by Michael Musgrove (Jira)

Michael Musgrove created JBTM-3197: -------------------------------------- Summary: Include an STM quickstart running on Quarkus (including native mode) Key: JBTM-3197 URL: https://issues.jboss.org/browse/JBTM-3197 Project: JBoss Transaction Manager Issue Type: Enhancement Components: Demonstrator, LRA, Quickstarts Affects Versions: 5.9.8.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next Add a quickstart that shows how to create an STM example running on Quarkus. The quickstart should also include instructions for building a native executable. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3190) Transform LRA coordinator runtime to Quarkus

by Anonymous (Jira)

[ https://issues.jboss.org/browse/JBTM-3190?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Martin Stefanko created pull request #1504 in GitHub ---------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Transform LRA coordinator runtime to Quarkus > -------------------------------------------- > > Key: JBTM-3190 > URL: https://issues.jboss.org/browse/JBTM-3190 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > [LRA coordinator|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-c...] is an essential part of Narayana LRA processing. It would be beneficial to move the runtime from [Thorntail|https://thorntail.io] to [Quarkus|https://quarkus.io] for faster startup times and better memory utilization. > If possible, one additional step can be to compile lra-coordinator to the native executable which can bump out the performance of the lra-coordinator docker image. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3190) Transform LRA coordinator runtime to Quarkus

by Martin Stefanko (Jira)

[ https://issues.jboss.org/browse/JBTM-3190?page=com.atlassian.jira.plugin.... ] Martin Stefanko reassigned JBTM-3190: ------------------------------------- Assignee: Martin Stefanko > Transform LRA coordinator runtime to Quarkus > -------------------------------------------- > > Key: JBTM-3190 > URL: https://issues.jboss.org/browse/JBTM-3190 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: LRA > Affects Versions: 5.9.8.Final > Reporter: Martin Stefanko > Assignee: Martin Stefanko > Priority: Major > > [LRA coordinator|https://github.com/jbosstm/narayana/tree/master/rts/lra/lra-c...] is an essential part of Narayana LRA processing. It would be beneficial to move the runtime from [Thorntail|https://thorntail.io] to [Quarkus|https://quarkus.io] for faster startup times and better memory utilization. > If possible, one additional step can be to compile lra-coordinator to the native executable which can bump out the performance of the lra-coordinator docker image. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3196) Upgrade to Artemis version 2.9.0

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3196?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Thomas Jenkinson created pull request #1503 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Upgrade to Artemis version 2.9.0 > -------------------------------- > > Key: JBTM-3196 > URL: https://issues.jboss.org/browse/JBTM-3196 > Project: JBoss Transaction Manager > Issue Type: Component Upgrade > Components: Build System > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > > The version in WildFly is 2.9.0 currently: https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/pom.xml#L297 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3196) Upgrade to Artemis version 2.9.0

by Thomas Jenkinson (Jira)

Thomas Jenkinson created JBTM-3196: -------------------------------------- Summary: Upgrade to Artemis version 2.9.0 Key: JBTM-3196 URL: https://issues.jboss.org/browse/JBTM-3196 Project: JBoss Transaction Manager Issue Type: Component Upgrade Components: Build System Reporter: Thomas Jenkinson Assignee: Thomas Jenkinson The version in WildFly is 2.9.0 currently: https://github.com/wildfly/wildfly/blob/18.0.0.Beta1/pom.xml#L297 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 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: ---------------------------------------- I have fixed the test to not hang but the underlying issue still needs looking at. Could it be cache full? > 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.5#713005)

5 years, 2 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: ---------------------------------------- And if so, why? > 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.5#713005)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3194) JDBC ConnectionManager has deadlock potential

by Thomas Jenkinson (Jira)

[ https://issues.jboss.org/browse/JBTM-3194?page=com.atlassian.jira.plugin.... ] Thomas Jenkinson updated JBTM-3194: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > JDBC ConnectionManager has deadlock potential > --------------------------------------------- > > Key: JBTM-3194 > URL: https://issues.jboss.org/browse/JBTM-3194 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Transactional Driver > Reporter: Thomas Jenkinson > Assignee: Thomas Jenkinson > Priority: Major > Fix For: 5.next > > > {code} > "Thread-461" #484 prio=5 os_prio=0 cpu=1.84ms elapsed=131863.84s tid=0x00007fc2f0e0e000 nid=0x420a waiting for monitor entry [0x00007fbf99de0000] > java.lang.Thread.State: BLOCKED (on object monitor) > at com.arjuna.ats.internal.jdbc.ConnectionManager.release(ConnectionManager.java) > - waiting to lock <0x0000000083000ca0> (a java.lang.Class for com.arjuna.ats.internal.jdbc.ConnectionManager) > at com.arjuna.ats.internal.jdbc.ConnectionImple.closeImpl(ConnectionImple.java:360) > at com.arjuna.ats.internal.jdbc.ConnectionImple.close(ConnectionImple.java:323) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest$1.afterCompletion(PoolingTest.java:129) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545) > - locked <0x000000008355f318> (a java.lang.Object) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:101) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1287) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest.lambda$test$0(PoolingTest.java:135) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest$$Lambda$70/0x0000000100147040.run(Unknown Source) > at java.lang.Thread.run(java.base@11/Thread.java:834) > "Thread-462" #485 prio=5 os_prio=0 cpu=3.72ms elapsed=131863.84s tid=0x00007fc2f0e10800 nid=0x420b in Object.wait() [0x00007fbf99bde000] > java.lang.Thread.State: WAITING (on object monitor) > at java.lang.Object.wait(java.base@11/Native Method) > - waiting on <0x00000000831d5830> (a java.util.HashSet) > at java.lang.Object.wait(java.base@11/Object.java:328) > at com.arjuna.ats.internal.jdbc.ConnectionManager.create(ConnectionManager.java:134) > - waiting to re-lock in wait() <0x00000000831d5830> (a java.util.HashSet) > - locked <0x0000000083000ca0> (a java.lang.Class for com.arjuna.ats.internal.jdbc.ConnectionManager) > at com.arjuna.ats.jdbc.TransactionalDriver.connect(TransactionalDriver.java:89) > at java.sql.DriverManager.getConnection(java.sql@11/DriverManager.java:677) > at java.sql.DriverManager.getConnection(java.sql@11/DriverManager.java:189) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest$1.beforeCompletion(PoolingTest.java:119) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:360) > - locked <0x00000000835638e0> (a java.lang.Object) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:91) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1287) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest.lambda$test$0(PoolingTest.java:135) > at com.hp.mwtests.ts.jdbc.basic.PoolingTest$$Lambda$70/0x0000000100147040.run(Unknown Source) > at java.lang.Thread.run(java.base@11/Thread.java:834) > {code} -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 2 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 September 2019