September 2015 - jbossts-issues - Jboss List Archives

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

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2115?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2115: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > 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 > Priority: Minor > 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 > We should aim to test everything -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2110) Investigate support for IBM ORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2110?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2110: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Investigate support for IBM ORB > ------------------------------- > > Key: JBTM-2110 > URL: https://issues.jboss.org/browse/JBTM-2110 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Components: JTS > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > Fix For: 5.next > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1854) Journal failures in CI test suite on JDKORB

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1854?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1854: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Journal failures in CI test suite on JDKORB > ------------------------------------------- > > Key: JBTM-1854 > URL: https://issues.jboss.org/browse/JBTM-1854 > Project: JBoss Transaction Manager > Issue Type: Bug > Components: Testing > Affects Versions: 5.0.0.M3 > Reporter: Michael Musgrove > Assignee: Gytis Trikleris > Fix For: 5.next > > Attachments: CurrentTests01_Test036.tar.gz, idlj-failures.tar.gz, testoutput.idlj.tar.run4.gz > > > The first CI job link includes: > CurrentTests01_Test036 > jtsremote JTSRemote_ImplicitPropagationTest > crashrecovery02_2 CrashRecovery02_2 - all of them > crashrecovery05_1 CrashRecovery05_1 Tests 1, 6, 7, 8, 9, 10 > crashrecovery12 CrashRecovery12_Test03 (55 failures - about half of them) > The second CI job link includes: > JTSRemote_ImplicitPropagationTest failure > CrashRecovery02_2_Test46 hang -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1340) BeanPopulator overhead needs looking into

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1340?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1340: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > BeanPopulator overhead needs looking into > ----------------------------------------- > > Key: JBTM-1340 > URL: https://issues.jboss.org/browse/JBTM-1340 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Common > Affects Versions: 4.17.2 > Environment: Mac OS 10.7 > Reporter: Mark Little > Assignee: Tom Jenkinson > Fix For: 5.next > > > During profiling, BeanPopulator can represent a 7% overhead. It may not seem like a lot, but for something as relatively simple as what BeanPopulator should be doing, it seems to be quite a bit. > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.coordinator.TxStats.enabled > 6.9% - 4,477 ms - 10,000 inv. com.arjuna.ats.arjuna.common.arjPropertyManager.getCoordinatorEnvironmentBean > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getDefaultInstance > 6.9% - 4,476 ms - 10,000 inv. com.arjuna.common.internal.util.propertyservice.BeanPopulator.getNamedInstance > 2.5% - 1,587 ms - 10,000 inv. java.lang.StringBuilder.<init> > 2.3% - 1,507 ms - 10,000 inv. java.lang.StringBuilder.toString > 0.0% - 320 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.containsKey > 0.0% - 61 µs - 10,000 inv. java.lang.Class.getName > 0.0% - 25 µs - 10,000 inv. java.util.concurrent.ConcurrentMap.get -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-1804) JTS remote tests not run and no code coverage

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-1804?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-1804: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > JTS remote tests not run and no code coverage > --------------------------------------------- > > Key: JBTM-1804 > URL: https://issues.jboss.org/browse/JBTM-1804 > Project: JBoss Transaction Manager > Issue Type: Task > Components: JTS, Testing > Affects Versions: 5.0.0.M3 > Reporter: Mark Little > Assignee: Amos Feng > Fix For: 5.next > > > The tests in .remote. package for JTS are not run by default. We should consider adding a build option so that they are run (will require some mods to the tests since many of them are client/server based - see associated Readme.txt files); don't run them by default since they will add delay to a normal build. > It would then be beneficial to have them instrumented by emma to get code coverage. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-855) Create an example showing integration with Spring

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-855?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-855: ------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Create an example showing integration with Spring > ------------------------------------------------- > > Key: JBTM-855 > URL: https://issues.jboss.org/browse/JBTM-855 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Demonstrator > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > Original Estimate: 1 week > Remaining Estimate: 1 week > > The main thing is to show the config but we need to provide an example that shows how to ensure the XAResources are available for recovery -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-741) Remove redundant XTS classes and code paths identified from coverage data

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-741?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated JBTM-741: ------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Remove redundant XTS classes and code paths identified from coverage data > ------------------------------------------------------------------------- > > Key: JBTM-741 > URL: https://issues.jboss.org/browse/JBTM-741 > Project: JBoss Transaction Manager > Issue Type: Task > Components: XTS > Affects Versions: 4.11.0 > Reporter: Andrew Dinn > Assignee: Gytis Trikleris > Fix For: 5.next > > > Coverage analysis of the XTS code base has idenitifed a lot of unexercised classes and code paths. These need pruning in order to simplify maintenance and testing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2481) Automate NRP

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2481?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2481: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Automate NRP > ------------ > > Key: JBTM-2481 > URL: https://issues.jboss.org/browse/JBTM-2481 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Release Process > Reporter: Tom Jenkinson > Assignee: Gytis Trikleris > Priority: Minor > Fix For: 5.next > > > There are a number of steps on NRP that could be automated using Jira API. > Lets try to do that: > https://community.jboss.org/wiki/NarayanaReleaseProcess -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2480) Provide documentation of how to integrate with Karaf

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2480?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2480: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > Provide documentation of how to integrate with Karaf > ---------------------------------------------------- > > Key: JBTM-2480 > URL: https://issues.jboss.org/browse/JBTM-2480 > Project: JBoss Transaction Manager > Issue Type: Task > Components: Documentation > Reporter: Tom Jenkinson > Assignee: Amos Feng > Fix For: 5.next > > > This should include recovery information -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTM-2476) When a transaction times out, print the stack traces of the threads involved

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/JBTM-2476?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated JBTM-2476: -------------------------------- Fix Version/s: 5.next (was: 5.2.4.Final) > When a transaction times out, print the stack traces of the threads involved > ---------------------------------------------------------------------------- > > Key: JBTM-2476 > URL: https://issues.jboss.org/browse/JBTM-2476 > Project: JBoss Transaction Manager > Issue Type: Enhancement > Components: Transaction Core > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 5.next > > > Would be useful to help understand what the code was doing when the transaction times out. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 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 2015