July 2018 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-3046: ---------------------------------------- The linked pull request upgrades the version of Undertow used for running the test. > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Michael Musgrove created pull request #1352 in GitHub ----------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3046?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3046: ----------------------------------- Attachment: threaddump.txt > REST-AT PerformanceTest occasionally hangs on Windows CI runs > ------------------------------------------------------------- > > Key: JBTM-3046 > URL: https://issues.jboss.org/browse/JBTM-3046 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Performance Testing > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > Attachments: threaddump.txt > > > The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest > See the attachment for the stacktraces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3046) REST-AT PerformanceTest occasionally hangs on Windows CI runs

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-3046: -------------------------------------- Summary: REST-AT PerformanceTest occasionally hangs on Windows CI runs Key: JBTM-3046 URL: https://issues.jboss.org/browse/JBTM-3046 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.9.0.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The test runs from the rts/at/tx/pom.xml module (org.jboss.narayana.rts:restat). The hanging thread seems to be a coordinator request to start an inVM REST-AT transaction. The coordinator is running in an Undertow container and the failing test is org.jboss.jbossts.star.test.PerformanceTest See the attachment for the stacktraces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2847) Static code analysis - check report and fix issues

by Ondra Chaloupka (JIRA)

[ https://issues.jboss.org/browse/JBTM-2847?page=com.atlassian.jira.plugin.... ] Ondra Chaloupka commented on JBTM-2847: --------------------------------------- additional static analysis refactoring at PR: https://github.com/jbosstm/narayana/pull/1349 > Static code analysis - check report and fix issues > -------------------------------------------------- > > Key: JBTM-2847 > URL: https://issues.jboss.org/browse/JBTM-2847 > Project: JBoss Transaction Manager > Issue Type: Task > Affects Versions: 5.5.1.Final > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Minor > Fix For: 5.5.2.Final > > > By going through static code analysis report of changes done during last a half year there are few issues that would be fine to be adjusted. > They are following > # at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple, > L614; com.arjuna.ats.internal.jta.transaction.jts.jca, L471 > (https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/jta/classes/com...) the calling method getCurrentTransactionId() potentially could end with > NullPointerException (caused by TransactionImple#getTransaction when `final BasicAction current = BasicAction.Current()` is null) > # possible resource leak - connection was ommitted to be closed > ## org.jboss.narayana.tomcat.jta.integration.TestExecutor > ## TestCommitMarkableResourceFailAfterCommitOrphan > # inner class SampleLockable of org.jboss.stm.STMVerticle could be static (http://station5.brq.redhat.com:8080/docs/en/findbugs/fb_checker_ref.html#...) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3043) REST-AT to JTA Bridge Quickstart failing

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-3043?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-3043: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST-AT to JTA Bridge Quickstart failing > ---------------------------------------- > > Key: JBTM-3043 > URL: https://issues.jboss.org/browse/JBTM-3043 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: REST > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > ------------------------------------------------------- > Running org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest > Tests run: 4, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 6.973 sec <<< FAILURE! - in org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest > testCommitWithTwoTasks(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.8 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testCommitWithTwoTasks(TaskResourceTest.java:147) > testRollback(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.094 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testRollback(TaskResourceTest.java:130) > testCommit(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.066 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testCommit(TaskResourceTest.java:111) > testRollbackWithTwoTasks(org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest) Time elapsed: 0.063 sec <<< FAILURE! > java.lang.AssertionError: expected:<201> but was:<500> > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.createTask(TaskResourceTest.java:190) > at org.jboss.narayana.quickstart.rest.bridge.inbound.jpa.test.TaskResourceTest.testRollbackWithTwoTasks(TaskResourceTest.java:169) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3030) Moving the tomcat-jta to the JWS web-servers repo

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3030?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Tom Jenkinson created pull request #232 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > Moving the tomcat-jta to the JWS web-servers repo > ------------------------------------------------- > > Key: JBTM-3030 > URL: https://issues.jboss.org/browse/JBTM-3030 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Tomcat > Reporter: Amos Feng > Assignee: Amos Feng > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3045) JTA CDI regression (or Standalone JTA 1.2 Quickstart failure)

by Laird Nelson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin.... ] Laird Nelson commented on JBTM-3045: ------------------------------------ Pull request filed: https://github.com/jbosstm/narayana/pull/1351 > JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) > ------------------------------------------------------------- > > Key: JBTM-3045 > URL: https://issues.jboss.org/browse/JBTM-3045 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > The recent changes to our JTA CDI support (https://issues.jboss.org/browse/JBTM-3044) have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The failure is: > {quote} > testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase) Time elapsed: 0.536 sec <<< ERROR! > javax.enterprise.inject.CreationException: Not a compound name: TransactionManager > {quote} > See for example CI run http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/c... > If the issue does turn out to be a regression then the priority needs to be marked as Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3045) JTA CDI regression (or Standalone JTA 1.2 Quickstart failure)

by Laird Nelson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin.... ] Issue was automatically transitioned when Laird Nelson created pull request #1350 in GitHub ------------------------------------------------------------------------------------------- Status: Pull Request Sent (was: Open) > JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) > ------------------------------------------------------------- > > Key: JBTM-3045 > URL: https://issues.jboss.org/browse/JBTM-3045 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > The recent changes to our JTA CDI support (https://issues.jboss.org/browse/JBTM-3044) have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The failure is: > {quote} > testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase) Time elapsed: 0.536 sec <<< ERROR! > javax.enterprise.inject.CreationException: Not a compound name: TransactionManager > {quote} > See for example CI run http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/c... > If the issue does turn out to be a regression then the priority needs to be marked as Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTM-3045) JTA CDI regression (or Standalone JTA 1.2 Quickstart failure)

by Laird Nelson (JIRA)

[ https://issues.jboss.org/browse/JBTM-3045?page=com.atlassian.jira.plugin.... ] Laird Nelson commented on JBTM-3045: ------------------------------------ The root cause is understood. This is not a regression. Briefly, the JBoss {{NamingContext}} class as used indirectly by the quickstart incorrectly expects that all {{Name}} instances supplied to, for example, {{lookup(Name)}} be {{CompoundName}} instances. The {{TransactionExtension}} class correctly (from the point of the JNDI specification) uses a {{CompositeName}} to lookup {{java:/TransactionManager}}, but the JBoss {{NamingContext}} rejects it because it is not a {{CompoundName}}. The workaround will be for the {{TransactionExtension}} class to supply a {{String}} ("{{java:/TransactionManager}}") instead of a hand-built {{CompositeName}}. Then non-compliant {{InitialContext}} implementations will continue to work as well as compliant ones. > JTA CDI regression (or Standalone JTA 1.2 Quickstart failure) > ------------------------------------------------------------- > > Key: JBTM-3045 > URL: https://issues.jboss.org/browse/JBTM-3045 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Demonstrator > Affects Versions: 5.9.0.Final > Reporter: Michael Musgrove > Priority: Critical > Fix For: 5.next > > > The recent changes to our JTA CDI support (https://issues.jboss.org/browse/JBTM-3044) have either caused a regression or the Standalone JTA 1.2 Quickstart needs updating. The failure is: > {quote} > testMandatoryTransactionWithExistingTransaction(org.jboss.narayana.quickstarts.jta.TestCase) Time elapsed: 0.536 sec <<< ERROR! > javax.enterprise.inject.CreationException: Not a compound name: TransactionManager > {quote} > See for example CI run http://narayanaci1.eng.hst.ams2.redhat.com/job/narayana-quickstarts/159/c... > If the issue does turn out to be a regression then the priority needs to be marked as Critical. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

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