November 2015 - jbossts-issues - Jboss List Archives

[JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2554?page=com.atlassian.jira.plugin.... ] Gytis Trikleris commented on JBTM-2554: --------------------------------------- http://albany.eng.hst.ams2.redhat.com/view/Narayana/job/narayana/979/ > CrashRecovery05_2 failures on JacORB > ------------------------------------ > > Key: JBTM-2554 > URL: https://issues.jboss.org/browse/JBTM-2554 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Reporter: Gytis Trikleris > Assignee: Michael Musgrove > Fix For: 5.next > > > crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) > crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) > crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) > crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) > crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) > crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) > crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) > crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2554) CrashRecovery05_2 failures on JacORB

by Gytis Trikleris (JIRA)

Gytis Trikleris created JBTM-2554: ------------------------------------- Summary: CrashRecovery05_2 failures on JacORB Key: JBTM-2554 URL: https://issues.jboss.org/browse/JBTM-2554 Project: JBoss Transaction Manager Issue Type: Bug Components: Testing Reporter: Gytis Trikleris Assignee: Michael Musgrove Fix For: 5.next crashrecovery05_2 CrashRecovery05_2_Test076 Fail (2m2.616s) crashrecovery05_2 CrashRecovery05_2_Test077 Fail (0m42.315s) crashrecovery05_2 CrashRecovery05_2_Test078 Fail (2m2.087s) crashrecovery05_2 CrashRecovery05_2_Test079 Fail (0m41.911s) crashrecovery05_2 CrashRecovery05_2_Test080 Fail (0m42.166s) crashrecovery05_2 CrashRecovery05_2_Test081 Fail (0m42.336s) crashrecovery05_2 CrashRecovery05_2_Test083 Fail (0m44.541s) crashrecovery05_2 CrashRecovery05_2_Test088 Fail (2m4.696s) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2498: --------------------------------- It looks like the quickstart jobs clone and build the narayana so it does not need to wget from the github > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2553) Investigate the test with byteman do not work with the jacoco

by Amos Feng (JIRA)

Amos Feng created JBTM-2553: ------------------------------- Summary: Investigate the test with byteman do not work with the jacoco Key: JBTM-2553 URL: https://issues.jboss.org/browse/JBTM-2553 Project: JBoss Transaction Manager Issue Type: Sub-task Reporter: Amos Feng Assignee: Amos Feng -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ] Amos Feng commented on JBTM-2498: --------------------------------- I send PR https://github.com/jbosstm/quickstart/pull/155 to wget the initializeJBoss.xml from the narayana repo > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2498) Incomplete BlackTie quickstart documentation

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2498?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2498: ---------------------------- Fix Version/s: 5.next > Incomplete BlackTie quickstart documentation > -------------------------------------------- > > Key: JBTM-2498 > URL: https://issues.jboss.org/browse/JBTM-2498 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: BlackTie, Demonstrator, Documentation > Affects Versions: 5.2.2 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The BlackTie README.md quickstart files are out of date with respect to running against the latest wildfly. > Ideally, the quickstarts should be standalone (and automatable - run.sh nearly works but not quite) so we need better instructions on how to configure, start and deploy to wildfly. > My ideal quickstart is one from which I can cut lines and paste into a terminal in order to get it working. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2552) Benchmark script should accept extra script arguments

by Michael Musgrove (JIRA)

Michael Musgrove created JBTM-2552: -------------------------------------- Summary: Benchmark script should accept extra script arguments Key: JBTM-2552 URL: https://issues.jboss.org/browse/JBTM-2552 Project: JBoss Transaction Manager Issue Type: Bug Components: Performance Testing Affects Versions: 5.2.7.Final Reporter: Michael Musgrove Assignee: Michael Musgrove Fix For: 5.next The launch script for running benchmarks (narayana/scripts/hudson/benchmark.sh in the repo https://github.com/jbosstm/performance) should propagate any script arguments through to the benchmark script. I plan to use this for configuring things like the transaction timeout value and to configure how many commit failures are tolerated before failing the job. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2115) Not all classes are under code coverage

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2115: ---------------------------------- Description: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml compensations/pom.xml txframework/pom.xml We should aim to test everything was: The following poms contain skipped classes for code coverage: ArjunaCore/arjuna/pom.xml ArjunaJTA/jdbc/pom.xml ArjunaJTA/jta/pom.xml ArjunaJTA/spi/pom.xml XTS/localjunit/pom.xml We should aim to test everything > Not all classes are under code coverage > --------------------------------------- > > Key: JBTM-2115 > URL: https://issues.jboss.org/browse/JBTM-2115 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Testing > Affects Versions: 5.0.1 > Reporter: Michael Musgrove > Assignee: Amos Feng > Fix For: 5.next > > > The following poms contain skipped classes for code coverage: > ArjunaCore/arjuna/pom.xml > ArjunaJTA/jdbc/pom.xml > ArjunaJTA/jta/pom.xml > ArjunaJTA/spi/pom.xml > XTS/localjunit/pom.xml > compensations/pom.xml > txframework/pom.xml > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2532) Enable code coverage for XTS

by Gytis Trikleris (JIRA)

[ https://issues.jboss.org/browse/JBTM-2532?page=com.atlassian.jira.plugin.... ] Gytis Trikleris updated JBTM-2532: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Enable code coverage for XTS > ---------------------------- > > Key: JBTM-2532 > URL: https://issues.jboss.org/browse/JBTM-2532 > Project: JBoss Transaction Manager > Issue Type: Sub-task > Components: Testing, XTS > Reporter: Gytis Trikleris > Assignee: Gytis Trikleris > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

[JBoss JIRA] (JBTM-2550) ClassNotFoundException when restore_state from the object store during recovering

by Amos Feng (JIRA)

[ https://issues.jboss.org/browse/JBTM-2550?page=com.atlassian.jira.plugin.... ] Amos Feng updated JBTM-2550: ---------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > ClassNotFoundException when restore_state from the object store during recovering > --------------------------------------------------------------------------------- > > Key: JBTM-2550 > URL: https://issues.jboss.org/browse/JBTM-2550 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Recovery > Reporter: Amos Feng > Assignee: Amos Feng > Priority: Critical > Fix For: 5.next > > > This exception happens with using the IBM MQ rar in the wildfly. > com.ibm.mq.connector.xa.XARWrapper is the serialize object. when the RecoveryManager tries to restore_state from the object record, it will load the class and threw CNFE as it can not access the XARWrapper classe in the RAR. Now we catch this exception and try to get from the helpers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues November 2015