June 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2420) BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s)

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2420?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2420: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > BlackTie hanging on all windows builds during btadmin: Transaction 0:ffff0a27a80e:-6a877d1b:555c3b97:8b has 1 heuristic participant(s) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTM-2420 > URL: https://issues.jboss.org/browse/JBTM-2420 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, REST > Reporter: Tom Jenkinson > Assignee: Amos Feng > Priority: Blocker > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana-catelyn/... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2427) btadmin.ListRunningInstanceIdsTest hang on the Linux

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2427?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2427: --------------------------------- It looks like related to the shutdown command which checks if the process is alive. > btadmin.ListRunningInstanceIdsTest hang on the Linux > ---------------------------------------------------- > > Key: JBTM-2427 > URL: https://issues.jboss.org/browse/JBTM-2427 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie > Reporter: Amos Feng > Assignee: Amos Feng > Fix For: 5.next > > > http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/PROFILE=... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2427) btadmin.ListRunningInstanceIdsTest hang on the Linux

by Amos Feng (JIRA)

Amos Feng created JBTM-2427: ------------------------------- Summary: btadmin.ListRunningInstanceIdsTest hang on the Linux Key: JBTM-2427 URL: https://issues.jboss.org/browse/JBTM-2427 Project: JBoss Transaction Manager Issue Type: Bug Components: BlackTie Reporter: Amos Feng Assignee: Amos Feng Fix For: 5.next http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/PROFILE=... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2426: ---------------------------------- Priority: Minor (was: Major) > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Priority: Minor > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 » TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove edited comment on JBTM-2308 at 6/5/15 5:45 AM: ---------------------------------------------------------------- Note that the junit tests for this work only asserted the creation of MBeans for the top level log and is the reason why our testing produced a false positive. The fix needs to make sure that the tests also assert the presence of MBeans for the participants. was (Author: mmusgrov): Note that the junit tests for this work only asserted the creation of MBeans for the top level log and is the reason why our testing produced a false positive. The fix needs to make sure that the tests also assert the presents of MBeans for the participants. > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.1.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove commented on JBTM-2308: ---------------------------------------- Note that the junit tests for this work only asserted the creation of MBeans for the top level log and is the reason why our testing produced a false positive. The fix needs to make sure that the tests also assert the presents of MBeans for the participants. > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.1.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2426?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2426: ---------------------------------- Attachment: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > XTS WSTFSC07-interop failure > ---------------------------- > > Key: JBTM-2426 > URL: https://issues.jboss.org/browse/JBTM-2426 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: XTS > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Attachments: com.jboss.transaction.wstf.interop.Sc007Test-output.txt > > > junit test failure: > {code} > Running com.jboss.transaction.wstf.interop.Sc007Test > Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! > test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! > junit.framework.AssertionFailedError: Conversation did not complete successfully > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) > test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! > com.arjuna.wst.TransactionRolledBackException: null > at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) > at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) > at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) > Results : > Failed tests: > Sc007Test.test3_10:176 Conversation did not complete successfully > Tests in error: > Sc007Test.test3_11:181 » TransactionRolledBack > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2308) New JTS record types are not showing up in the tooling

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2308?page=com.atlassian.jira.plugin.... ] Michael Musgrove reopened JBTM-2308: ------------------------------------ I am reopening because the participants of these transaction types are not being instrumented. > New JTS record types are not showing up in the tooling > ------------------------------------------------------ > > Key: JBTM-2308 > URL: https://issues.jboss.org/browse/JBTM-2308 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Tooling > Affects Versions: 4.17.23, 5.0.3 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 4.17.27, 5.1.0 > > > When a JTS transaction record has participants of type CosTransactions/XAResourceRecord which are in the same object store then the tooling should create MBeans to represent them as participants of the JTS record. > I have marked the type to enhancement since JTS participants do show up in the tooling (using records that are in-lined with records of type /StateManager/BasicAction/TwoPhaseCoordinator/ArjunaTransactionImple). Note that the tooling implementation does not look at records of type CosTransactions/XAResourceRecord (the only potentially useful information for the user here is the Xid and I will leave that until someone asks for it). > What is missing is instrumentation for new types: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2426) XTS WSTFSC07-interop failure

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2426: -------------------------------------- Summary: XTS WSTFSC07-interop failure Key: JBTM-2426 URL: https://issues.jboss.org/browse/JBTM-2426 Project: JBoss Transaction Manager Issue Type: Bug Components: XTS Affects Versions: 5.1.1 Reporter: Michael Musgrove Assignee: Gytis Trikleris junit test failure: {code} Running com.jboss.transaction.wstf.interop.Sc007Test Tests run: 15, Failures: 1, Errors: 1, Skipped: 0, Time elapsed: 326.369 sec <<< FAILURE! test3_10(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 212.002 sec <<< FAILURE! junit.framework.AssertionFailedError: Conversation did not complete successfully at junit.framework.Assert.fail(Assert.java:57) at junit.framework.Assert.assertTrue(Assert.java:22) at junit.framework.TestCase.assertTrue(TestCase.java:192) at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_10(Sc007TestCase.java:474) at com.jboss.transaction.wstf.interop.Sc007Test.test3_10(Sc007Test.java:176) test3_11(com.jboss.transaction.wstf.interop.Sc007Test) Time elapsed: 1.608 sec <<< ERROR! com.arjuna.wst.TransactionRolledBackException: null at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:65) at com.jboss.transaction.wstf.interop.Sc007TestCase.test3_11(Sc007TestCase.java:495) at com.jboss.transaction.wstf.interop.Sc007Test.test3_11(Sc007Test.java:181) Results : Failed tests: Sc007Test.test3_10:176 Conversation did not complete successfully Tests in error: Sc007Test.test3_11:181 » TransactionRolledBack {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2404) narayana-codeCoverage CI job is not producing any output

by Michael Musgrove (JIRA)

[ https://issues.jboss.org/browse/JBTM-2404?page=com.atlassian.jira.plugin.... ] Michael Musgrove updated JBTM-2404: ----------------------------------- Status: Pull Request Sent (was: Pull Request Sent) Git Pull Request: https://github.com/jbosstm/narayana/pull/845, https://github.com/jbosstm/narayana/pull/862 (was: https://github.com/jbosstm/narayana/pull/845) Added another PR because: JBTM-1339 copied the openjdk-orb jar to the build directory but this causes jacoco to try to instrument it. I have changed the pom so that the jar is now referenced via the local maven repository. > narayana-codeCoverage CI job is not producing any output > -------------------------------------------------------- > > Key: JBTM-2404 > URL: https://issues.jboss.org/browse/JBTM-2404 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Configuration > Affects Versions: 5.1.1 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 5.next > > > The job config fails to produce the report if we don't run any qa tests during a build. See the following job for example: > http://albany.eng.hst.ams2.redhat.com/job/narayana-codeCoverage/194/conso... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 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 June 2015